Frequently asked questions

No. SvitloPulse is an independent service. Official information comes from distribution system operators and Ukrenergo. We gather their schedules in one place and add independent signals.

GPV is the hourly outage schedule. Consumers are split into 6 queues, each into 2 subqueues, 12 groups in all. Power is cut in turns, so in any hour only some groups are off. In Kyiv DTEK uses its own scheme of up to 60 groups.

The queue number is on your bill or in your operator’s account, and on the operator’s website by address. We store only the queue number, not your address.

Partly. On the map, in the “Your home” block, there is a “Find by address” search: region, city, street, house. It works only for the regions the server lists (currently Kyiv and Dnipro, Yasno data). We do not store the address, only the queue number stays. If the lookup is unavailable or your region is not listed, pick the queue manually.

No. The map, schedules and history are open without signing in. Reminders need only Telegram or a browser notification permission.

There is data for regions where the operator publishes a usable schedule. For the others we show “No data”. Current coverage and its limits are described on the “Data sources” page.

As accurate as the operator’s schedule, and only at queue and region level. We do not promise house-level accuracy. If the schedule and reality diverge, “Outage possible” or an emergency regime may show it.

The operator marked the time as possible rather than certain, or the signals contradict the schedule and neither side prevails. It is neither “on” nor “off”, just an honest “maybe”.

The operator does not publish a schedule in a machine-readable form or the data has not been updated for a long time. We do not guess: unknown is grey, never green.

It is the end of the current interval in the schedule, so it is a planned time. If an outage is an emergency one, extended, or the schedule changed, the real time will differ. The bot tells you about schedule changes.

The operator’s data is older than 45 minutes. It is a warning that the operator has not published anything for a while, not a map error.

The operator shows its own schedule. We put schedules of many operators on one map, keep the history of their changes and add independent signals where there are any. But the source of a schedule is always the operator.

Yes, in the browser. In the “Your home” block switch on “Browser notifications”, allow them in the browser prompt, and we warn you 15, 30 or 60 minutes before your queue’s outage. It is Web Push: it works in Chrome, Edge, Firefox and Safari. No separate app is needed.

iOS allows website notifications only for sites added to the Home Screen. In Safari tap Share, then “Add to Home Screen”, open SvitloPulse from its icon and switch notifications on there. Until then the button shows a hint. Telegram works without this.

Turn the switch off in the “Your home” block: the subscription is removed from our server and from the browser. You can also block notifications for the site in the browser settings.

Open the bot and pick a region, an operator and a queue. A faster way: press “Subscribe” on a queue page and the bot creates the subscription from a single-use link valid for 30 minutes.

A chosen time before an outage (5 to 180 minutes, up to three reminders), when power goes off per schedule with the expected restoration time, when it should be back, and also when tomorrow’s schedule is published or emergency outages are in force.

Yes, with /quiet 23-7 (Kyiv hours). Turn quiet hours off with /quiet off.

Up to 10. Remove extra ones with /my.

For websites, READMEs and smart homes there is a badge (SVG), an iframe card and a Home Assistant example: all on the “Widgets and badges” page. There are no native iOS or Android home screen widgets.

Yes. A router, Raspberry Pi, ESP32 or Home Assistant sends a request to a secret address once a minute, and when the requests stop, power is probably out. Instructions and sensor creation are on the “Power sensor” page. One sensor changes nothing publicly: we never show individual sensors, and a signal counts only when at least five sensors of one queue send it.

For Telegram reminders, a chat id and the queues you picked. For browser notifications, your browser’s technical subscription address and the queue you picked. For a sensor, a token and a queue. For discussions and reports, an anonymous device cookie. The address you type to find a queue is not stored. We do not ask for a name, phone number, address or location.

The /forget command in the bot deletes your subscriptions and Telegram data. Browser notifications are switched off with the switch in the “Your home” block. A sensor is deleted by its token on the “Power sensor” page. You can delete the device cookie in your browser settings.

A map of substations and lines would be a map of targets, and a single signal is someone’s home. So public data is aggregated to queue and region level, and signals appear with a delay of at least 30 minutes and only when there are at least five.

Yes, an open JSON API with no key: /api/v1. There are per-IP rate limits. It is described on the API page.

Yes, for those who need more than the free limits: keys, indicative quotas and webhooks for an outage start, power restoration and a schedule change. Keys are issued by the service operator by hand, there is no billing or SLA, and for commercial use the licensing of operators’ data has to be agreed first. Details are on the “For developers” page.

If an operator changed a schedule and we have not yet, wait for the refresh: data is recomputed about every 30 seconds. If the mismatch persists, mention it in the queue or region discussion.