Is GitHub Enterprise Cloud JP down?

Last checked 8m ago
Current status
GitHub Enterprise Cloud JP is up

No incidents right now.

Get alerts when GitHub Enterprise Cloud JP breaks →

Free · no credit card

Official status page: https://jp.githubstatus.com/posts/dashboard · Polled every 5 minutes · 20 components tracked

Real-time GitHub Enterprise Cloud JP status, recent outages, and incident history — pulled directly from GitHub Enterprise Cloud JP's official status page at https://jp.githubstatus.com/posts/dashboard every 5 minutes. Pingoru tracks 20 GitHub Enterprise Cloud JP services and has captured 8 incidents in the last 90 days (99.58% uptime). Get email, Slack, Discord, or webhook alerts the moment GitHub Enterprise Cloud JP reports a new incident — free for 5 monitors, no credit card.

Users who monitor GitHub Enterprise Cloud JP also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
GitHub Enterprise Cloud JP uptime 99.58% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Incident with Pull Requests
    Resolved 1h 52m
    Started Apr 23, 2026, 07:50 PM UTC · Resolved Apr 23, 2026, 09:43 PM UTC
    Pull Requests
    4 updates · show timeline
    • investigating · Apr 23, 2026, 07:50 PM UTC

      We are investigating reports of degraded performance for Pull Requests

    • investigating · Apr 23, 2026, 07:58 PM UTC

      We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.

    • investigating · Apr 23, 2026, 09:43 PM UTC

      Pull Requests is operating normally.

    • resolved · Apr 23, 2026, 09:43 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  2. Disruption with users unable to start Claude and Codex agent task from the web
    Resolved 13m
    Started Apr 23, 2026, 07:29 PM UTC · Resolved Apr 23, 2026, 07:42 PM UTC
    3 updates · show timeline
    • investigating · Apr 23, 2026, 07:29 PM UTC

      We are investigating reports of impacted performance for some GitHub services.

    • investigating · Apr 23, 2026, 07:33 PM UTC

      We have identified the root cause of the issue and are working on mitigation.

    • resolved · Apr 23, 2026, 07:42 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  3. Disruption with some GitHub services
    Resolved 2h 50m
    Started Apr 22, 2026, 07:53 PM UTC · Resolved Apr 22, 2026, 10:43 PM UTC
    Issues
    6 updates · show timeline
    • investigating · Apr 22, 2026, 07:53 PM UTC

      We are investigating reports of impacted performance for some GitHub services.

    • investigating · Apr 22, 2026, 07:55 PM UTC

      Issues is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 22, 2026, 08:02 PM UTC

      Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

    • investigating · Apr 22, 2026, 08:37 PM UTC

      We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.

    • investigating · Apr 22, 2026, 10:09 PM UTC

      We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

    • resolved · Apr 22, 2026, 10:43 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  4. Disruption with Copilot chat and Copilot Coding Agent
    Resolved 3h 42m
    Started Apr 22, 2026, 03:35 PM UTC · Resolved Apr 22, 2026, 07:18 PM UTC
    8 updates · show timeline
    • investigating · Apr 22, 2026, 03:35 PM UTC

      We are investigating reports of impacted performance for some GitHub services.

    • investigating · Apr 22, 2026, 03:43 PM UTC

      We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.

    • investigating · Apr 22, 2026, 04:24 PM UTC

      We continue to work on mitigation for Copilot chat and cloud agent.

    • investigating · Apr 22, 2026, 04:58 PM UTC

      Mitigation is progressing for Copilot chat and cloud agent.

    • investigating · Apr 22, 2026, 05:40 PM UTC

      Mitigation is progressing for Copilot chat and cloud agent recovery.

    • investigating · Apr 22, 2026, 05:49 PM UTC

      We are now seeing recovery for Copilot cloud agent.

    • investigating · Apr 22, 2026, 06:05 PM UTC

      Copilot cloud agent and chat are mitigated for github.com.

    • resolved · Apr 22, 2026, 07:18 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

See the full GitHub Enterprise Cloud JP outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 8 incidents
  • Incident with Pull Requests Resolved
    Started Apr 23, 2026, 07:50 PM UTC · Resolved Apr 23, 2026, 09:43 PM UTC · 1h 52m
  • Disruption with users unable to start Claude and Codex agent task from the web Resolved
    Started Apr 23, 2026, 07:29 PM UTC · Resolved Apr 23, 2026, 07:42 PM UTC · 13m
  • Disruption with some GitHub services Resolved
    Started Apr 22, 2026, 07:53 PM UTC · Resolved Apr 22, 2026, 10:43 PM UTC · 2h 50m
  • Disruption with Copilot chat and Copilot Coding Agent Resolved
    Started Apr 22, 2026, 03:35 PM UTC · Resolved Apr 22, 2026, 07:18 PM UTC · 3h 42m
  • Disruption with some GitHub services Resolved
    Started Apr 14, 2026, 02:16 AM UTC · Resolved Apr 14, 2026, 06:08 AM UTC · 3h 52m
  • Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard Resolved
    Started Apr 10, 2026, 01:07 PM UTC · Resolved Apr 10, 2026, 01:28 PM UTC · 21m
  • Copilot Coding Agent failing to start some jobs Resolved
    Started Apr 02, 2026, 04:18 PM UTC · Resolved Apr 02, 2026, 04:30 PM UTC · 12m
  • Incident with Pull Requests: High percentage of 500s Resolved
    Started Mar 31, 2026, 03:05 PM UTC · Resolved Apr 01, 2026, 01:11 PM UTC · 22h 5m

See GitHub Enterprise Cloud JP in your Pingoru dashboard

Monitor GitHub Enterprise Cloud JP alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add GitHub Enterprise Cloud JP to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every GitHub Enterprise Cloud JP incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just GitHub Enterprise Cloud JP or see every provider at once.

Maintenance calendar

Scheduled GitHub Enterprise Cloud JP maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every GitHub Enterprise Cloud JP status change, one inbox

Pingoru watches GitHub Enterprise Cloud JP's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

GitHub Enterprise Cloud JP reports on 20 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route GitHub Enterprise Cloud JP alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming GitHub Enterprise Cloud JP maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy GitHub Enterprise Cloud JP services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching GitHub Enterprise Cloud JP from the same account, with per-user notification preferences for any monitor.

Get notified on GitHub Enterprise Cloud JP status changes

Pingoru watches GitHub Enterprise Cloud JP's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring GitHub Enterprise Cloud JP free

Monitor GitHub Enterprise Cloud JP along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add GitHub Enterprise Cloud JP and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track GitHub Enterprise Cloud JP uptime & incident history

See 90 days of GitHub Enterprise Cloud JP uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See GitHub Enterprise Cloud JP uptime history

Frequently asked questions

What is GitHub Enterprise Cloud JP's uptime?
Over the last 90 days, GitHub Enterprise Cloud JP reported 99.58% uptime on its official status page. That figure is calculated from the public incident timeline at https://jp.githubstatus.com/posts/dashboard — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see GitHub Enterprise Cloud JP's uptime history rolling forward in real time.
Has GitHub Enterprise Cloud JP had outages in 2026?
Yes — GitHub Enterprise Cloud JP has had 8 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last GitHub Enterprise Cloud JP outage?
The most recent GitHub Enterprise Cloud JP incident was "Incident with Pull Requests", which started on April 23, 2026 and was resolved on April 23, 2026. Pingoru captured this directly from https://jp.githubstatus.com/posts/dashboard. See the full incident card above for affected components and the update timeline.
How often does GitHub Enterprise Cloud JP have outages?
Based on the last 90 days, GitHub Enterprise Cloud JP averages 2.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is GitHub Enterprise Cloud JP's status page?
GitHub Enterprise Cloud JP's official status page is https://jp.githubstatus.com/posts/dashboard. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is GitHub Enterprise Cloud JP down right now?
GitHub Enterprise Cloud JP is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment GitHub Enterprise Cloud JP reports a change. Current status is based on 20 tracked services.
How does Pingoru know if GitHub Enterprise Cloud JP is down?
We read https://jp.githubstatus.com/posts/dashboard directly, using GitHub Enterprise Cloud JP's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when GitHub Enterprise Cloud JP has an outage?
Create a free Pingoru account and add GitHub Enterprise Cloud JP as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
GitHub Enterprise Cloud JP's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real GitHub Enterprise Cloud JP incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real GitHub Enterprise Cloud JP issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official GitHub Enterprise Cloud JP status?
We use GitHub Enterprise Cloud JP's own status page at https://jp.githubstatus.com/posts/dashboard and cross-reference their homepage (https://github.com). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked GitHub Enterprise Cloud JP components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch GitHub Enterprise Cloud JP's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor GitHub Enterprise Cloud JP free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →