Skip to content
PulseWatchOUTAGE.INTEL
GitHub logo

Productivity

Is GitHub down right now?

NormalOfficial status last polled Oct 3, 2026 08:25 UTCgithub.comOfficial status page

Code hosting, version control, and developer collaboration.

Are you on the GitHub team and see something inaccurate? Report it to us. We respond within one business day.

Is GitHub down right now?

No. GitHub has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 3, 2026 08:27 UTC

Normal

GitHub is operating normally

As of Oct 3, 2026 08:27 UTC

No elevated reports in the last 15 minutes. Baseline 8 reports/hour.

Reports 24h

0

Last incident

Oct 1, 2026 18:25 UTC

Trend

0/15m

Baseline

8/hr

Observed health

100/100

3 of 3 assessed samples succeeded within their latency target.

5/5 responses validated in the last 15 minutes. 2 successful samples have no qualified latency target.

1 inconclusive samples excluded; they do not establish health.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for GitHub.

11

Incident days

19

No recorded incident

54h 8m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for GitHub. Hover a day for detail.

Sep 4Sep 9Sep 14Sep 19Sep 24Sep 2901234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

11

Days with incidents

2 incidents

Busiest day

54h 8m

Recorded duration

Report volume

0 reports in last 24H

08:15 AM11:45 AM03:15 PM06:45 PM10:15 PM01:45 AM05:15 AM00.751.52.253baseline 2

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

GitHub: vendor-reported minor incident on October 1 (tracked 3h 33m)

Oct 1, 02:52 PM → Oct 1, 06:25 PM · 3h 33m · medium

GitHub reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3h 33m, from Thu, 01 Oct 2026 14:52:17 GMT to Thu, 01 Oct 2026 18:25:36 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3h 33m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Oct 1, 02:52 PM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 02:52 PM

    Status updated: possible issue

  3. Oct 1, 06:25 PM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 02:52 PM

    GitHub reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

92.5%

90-day uptime

0.0%

Calculated from GitHub's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 2:52:17 PM · 3h 33m

02:52 PM06:25 PM
Detection10/1/2026, 2:52:17 PM · 1d ago

Detected — medium severity

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 1:47:17 PM · 49 min

01:47 PM02:36 PM
Detection10/1/2026, 1:47:17 PM · 1d ago

Detected — medium severity

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/28/2026, 9:21:44 PM · 1h 29m

09:21 PM10:51 PM
Detection9/28/2026, 9:21:44 PM · 4d ago

Detected — medium severity

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/24/2026, 4:55:55 PM · 4h 29m

04:55 PM09:25 PM
Detection9/24/2026, 4:55:55 PM · 8d ago

Detected — medium severity

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/23/2026, 10:16:56 AM · 19h 4m

10:16 AM05:21 AM
Detection9/23/2026, 10:16:56 AM · 9d ago

Detected — medium severity

GitHub: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment GitHub enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
8
Open threshold
3x

Official site

github.com