Example status board by ShadowGraphMake it your own

Telegram status

Live · checked 3 min ago

All systems operational

4 of 4 systems reporting

Availability
99.980%
over 13 days measured
SLA 99.9%
4 of 4
within allowed downtime in October
Disruptions
0
detected in 30 days
Median response
815 ms
last 7 days

Services

  • Telegram100%
    Since 8 OctImperva (Incapsula) · median 368 msToday
    October: 0 of 45 min allowed downtime used
  • Telegram Web100%
    Since 8 OctImperva (Incapsula) · median 284 msToday
    October: 0 of 45 min allowed downtime used
  • Telegram Bot API100%
    Since 8 OctImperva (Incapsula) · median 825 msToday
    October: 0 of 45 min allowed downtime used
  • Telegram links (t.me)99.82%
    Since 8 OctImperva (Incapsula) · median 815 msToday
    October: 5 of 45 min allowed downtime used

Shared risk

What these tools have in common underneath

4 of 4 depend on Imperva (Incapsula) for content delivery. One incident there can reach all of them at the same time, even when each vendor's own status page looks fine.

HostingNot observable
Content deliveryImperva (Incapsula) 4
DNSGoogle Cloud DNS 4

Recent events

Last 30 days, from three independent sources

Nothing to report in the last 30 days.