Glitched lighting due to failed light update.
Minecraft doesn't recalculate lighting of blocks all the time, only when events that have a potential to change it happen. Otherwise, light level is one of properties of every block, stored, saved to disk, restored as you enter the area with given block, generally persistent.
2b2t runs on a Spigot or derivative server, not vanilla - and the server has a number of optimizations aimed at reducing the excessive lag typical to 2b2t.
queue-light-updates
is a Spigot property that allows distributing queued light updates over time, reducing lag as a lot of updates at once could really slow the server; something similar is a standard in vanilla since version 1.14.
That means, light updates don't follow immediately, as the events that require them happen - for example, player breaking a torch - but are deferred to when the server can catch up to them. They are scheduled to be calculated, and the list of pending updates is only kept in RAM. If something happens that disrupts the process, for example a server crash - the update is forgotten and the world lighting remains in an invalid state.
Due to chaotic, secretive and non-vanilla nature of 2b2t, it's unlikely this could be replicated on purpose there, but for 1.15-1.16 vanilla, a reliable, if complex, technique (that does involve crashing the server at specific point!) has been developed to replicate this, and much more complex effects.
Light suppression explained
Showcase: