Example status board by ShadowGraphMake it your own

Slack status

Live · checked 3 min ago

All systems operational

4 of 4 systems reporting

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

Services

  • SlackOfficial status100%
    Since 8 OctAmazon Web Services · median 338 msToday
    October: 0 of 45 min allowed downtime used
  • Slack APIOfficial status100%
    Since 8 OctAmazon Web Services · median 118 msToday
    October: 0 of 45 min allowed downtime used
  • Slack webhooksOfficial status100%
    Since 8 OctAmazon Web Services · median 567 msToday
    October: 0 of 45 min allowed downtime used
  • Slack filesOfficial status100%
    Since 8 OctAmazon Web Services · Amazon Web Services (CloudFront) · median 579 msToday
    October: 0 of 45 min allowed downtime used

Shared risk

What these tools have in common underneath

4 of 4 depend on Amazon Web Services for hosting. One incident there can reach all of them at the same time, even when each vendor's own status page looks fine.

HostingAmazon Web Services 4
Content deliveryAmazon Web Services (CloudFront) 1 · unknown 3
DNSAWS Route 53 4

Recent events

Last 30 days, from three independent sources
  1. 21 Sept, 23:26 UTC
    Amazon Web Services notice

    Increased Error Rates (ec2 us-east-1)

    58 min · Slack webhooks, Slack, Slack API