Example status board by ShadowGraphMake it your own

Engineering tools status

Live · checked 3 min ago

All systems operational

8 of 8 systems reporting

Availability
99.947%
over 13 days measured
SLA 99.9%
8 of 8
within allowed downtime in October
Ahead of the vendor
1
incident we saw before it was posted
Median response
250 ms
last 7 days

Services

  • GitHub APIOfficial status100%
    Since 8 OctGitHub (own network) · median 97 msToday
    October: 0 of 45 min allowed downtime used
  • GitHub Actions results99.79%
    Since 8 OctMicrosoft Azure · median 274 msToday
    October: 35 of 45 min allowed downtime used
  • Bitbucket APIOfficial status99.79%
    Since 8 OctAmazon Web Services · median 355 msToday
    October: 35 of 45 min allowed downtime used
  • Atlassian APIOfficial status100%
    Since 8 OctAmazon Web Services · Amazon Web Services (CloudFront) · median 250 msToday
    October: 0 of 45 min allowed downtime used
  • Stripe APIOfficial status100%
    Since 8 OctAmazon Web Services · median 100 msToday
    October: 0 of 45 min allowed downtime used
  • Twilio APIOfficial status100%
    Since 8 OctAmazon Web Services · Amazon Web Services (CloudFront) · median 90 msToday
    October: 0 of 45 min allowed downtime used
  • Datadog USOfficial status100%
    Since 8 OctAmazon Web Services · median 65 msToday
    October: 0 of 45 min allowed downtime used
  • Notion API100%
    Since 8 OctNotion Labs · median 275 msToday
    October: 0 of 45 min allowed downtime used

Shared risk

What these tools have in common underneath

7 of 8 depend on AWS Route 53 for DNS. One incident there can reach these at the same time, even when each vendor's own status page looks fine.

HostingAmazon Web Services 5 · GitHub (own network) 1 · Notion Labs 1
Content deliveryAmazon Web Services (CloudFront) 2 · unknown 6
DNSAWS Route 53 7 · Cloudflare 1

Recent events

Last 30 days, from three independent sources
  1. 20 Oct, 16:28 UTC
  2. 20 Oct, 15:43 UTC
    Declared by twilio.com

    WhatsApp Embedded Signup Configuration Failures

    ongoing · Twilio API
  3. 20 Oct, 10:46 UTC
  4. 20 Oct, 05:28 UTC
  5. 20 Oct, 02:05 UTC
  6. 19 Oct, 15:49 UTC
  7. 15 Oct, 18:31 UTC
    Declared by github.com

    CCA Automations are delayed when starting an Automation

    24 min · GitHub API
  8. 15 Oct, 10:07 UTC
    Declared by bitbucket.orgOur checks saw it 26 min before the vendor posted

    Bitbucket Cloud - Service Disruption

    2.0 h · Bitbucket API
  9. 15 Oct, 10:06 UTC
    Detected by probes

    Bitbucket API unreachable (HTTP 503)

    10 min · Bitbucket API
  10. 15 Oct, 09:41 UTC
    Detected by probes

    Bitbucket API unreachable (HTTP 503)

    35 min · Bitbucket API
  11. 14 Oct, 00:12 UTC
    Declared by github.com

    [Retroactive] Actions workflow run logs delayed

    resolved · GitHub API
  12. 12 Oct, 12:21 UTC
    Declared by github.com

    Incident with Actions, Pull Requests and Issues

    7.9 h · GitHub API