EVE Online runs on one clock. Every timer, every killmail, every downtime is UTC, and it never shifts for daylight saving. That is deliberate. An alliance spread across the US, Europe and Australia needs a single time everyone agrees on. The cost is that "form up at 20:00" means one thing to the FC who wrote it and something else to the pilot reading it.

Why post a Discord timestamp instead of a time

Discord renders a timestamp in each reader's own time zone. Drop one into a fleet ping for 20:00 EVE time and an American sees an afternoon, a European sees late evening, and an Australian sees breakfast the next morning. Nobody works out the offset in their head and nobody shows up an hour late. The relative format is better again for a countdown, because it keeps updating itself as the op approaches.

Why share a link

Not everything happens in Discord. Forum posts, spreadsheets, a group chat somewhere else. A link like evetime.io/?t=1789156800 opens this page on that exact moment, shown in the reader's local time, with a live countdown running. Pick the time once, send the link, and let everyone else's browser do the conversion.

Does EVE observe daylight saving?

No. EVE time is UTC all year round. If your country runs daylight saving, your offset to EVE shifts by an hour twice a year, which is why the same op looks like it moves every spring and fall. Much of the world does not observe it at all, including most of Asia, and there the gap to EVE never changes.

Is EVE time the same as GMT?

For much of the year, yes. But the UK switches to BST in summer and EVE does not, so they part company for about seven months.