Tweets

You blocked @githubstatus

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @githubstatus

  1. 5 minutes ago

    We have rolled out a fix and are monitoring recovery.

    Undo
  2. 16 minutes ago

    We continue to investigate elevated errors and timeouts across GitHub services

    Undo
  3. 44 minutes ago

    We are investigating reports of service unavailability.

    Undo
  4. 50 minutes ago

    We are investigating reports of degraded performance.

    Undo
  5. Mar 22

    Everything operating normally.

    Undo
  6. Mar 22

    Delays for Actions jobs have recovered. We are continuing to monitor.

    Undo
  7. Mar 22

    We continue to remediate the cause of Actions delays.

    Undo
  8. Mar 22

    We have identified the source of the delays and are working to remediate.

    Undo
  9. Mar 22

    We are investigating delays in running Action jobs on Linux.

    Undo
  10. Mar 12

    Everything operating normally.

    Undo
  11. Mar 12

    Currently investigating increase in Pages build failures.

    Undo
  12. Mar 5

    Everything operating normally.

    Undo
  13. Mar 5

    We are monitoring service recovery. We are processing a backlog of notifications.

    Undo
  14. Mar 5

    We are currently investigating a delay in notification delivery.

    Undo
  15. Feb 27

    Everything operating normally.

    Undo
  16. Feb 27

    Error rates across have now subsided and we continue to monitor recovery.

    Undo
  17. Feb 27

    We continue to investigate the issues with GitHub services and will shift to a slower update cadence to provide more meaningful updates going forward.

    Undo
  18. Feb 27

    We continue to investigate the source of increased errors affecting services.

    Undo
  19. Feb 27

    We are continuing to investigate elevated error rates across and will provide updates when we have them.

    Undo
  20. Feb 27

    We are investigating reports of increased API errors and webhook latency.

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·