by HonkWatch

Is GitHub Packages down in Mongolia?

No problems reported with GitHub Packages right now

Mongolia No reports in the last hour checked just now
GitHub Packages reports no current incident. Updated 6 Nov, 20:42 UTC, just now · Official status page
Report a problemFollow community reports
Change country

Reports from people in Mongolia

Last 24 hours · Mongolia · times in UTC

0 reports

No community reports in the last 24 hours from Mongolia. Having trouble? Add your report.

024 00:0006:0012:0018:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 20:42 UTC

Report a problem with GitHub Packages

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Mongolia

Monitor the provider status with HonkWatch

Get monitoring alerts for GitHub Packages

HonkWatch watches the GitHub Packages status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. GitHub Packages is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Mongolia. The report chart above is filtered to Mongolia.

Our own checks of github.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Amsterdam: loaded in 38 ms Frankfurt: loaded in 12 ms Tel Aviv: loaded in 26 ms New Jersey: loaded in 64 ms Atlanta: loaded in 136 ms Madrid: loaded in 110 ms Santiago: loaded in 208 ms Toronto: loaded in 97 ms London: loaded in 19 ms Tokyo: loaded in 24 ms Delhi: loaded in 108 ms Mumbai: loaded in 45 ms Port Louis: loaded in 182 ms Seattle: loaded in 28 ms Sydney: loaded in 58 ms Melbourne: loaded in 70 ms Cape Town: loaded in 124 ms Warsaw: loaded in 78 ms St. Louis: loaded in 231 ms Jakarta: loaded in 86 ms São Paulo: loaded in 32 ms Los Angeles: loaded in 284 ms Dallas: loaded in 164 ms New York: loaded in 37 ms Seoul: loaded in 23 ms Hong Kong: loaded in 149 ms Singapore: loaded in 19 ms Querétaro: loaded in 243 ms Hamina: loaded in 166 ms Bangalore: loaded in 86 ms Johannesburg: loaded in 29 ms Portsmouth: loaded in 37 ms Doha: loaded in 195 ms Osaka: loaded in 52 ms Lauterbourg: loaded in 45 ms
  • AmsterdamReachable38 ms, just now
  • FrankfurtReachable12 ms, just now
  • Tel AvivReachable26 ms, just now
  • New JerseyReachable64 ms, just now
  • AtlantaReachable136 ms, just now
  • MadridReachable110 ms, just now
  • SantiagoReachable208 ms, just now
  • TorontoReachable97 ms, just now
  • LondonReachable19 ms, just now
  • TokyoReachable24 ms, 1 min ago
  • DelhiReachable108 ms, 1 min ago
  • MumbaiReachable45 ms, 1 min ago
  • Port LouisReachable182 ms, 1 min ago
  • SeattleReachable28 ms, 4 min ago
  • SydneyReachable58 ms, 5 min ago
  • MelbourneReachable70 ms, 5 min ago
  • Cape TownReachable124 ms, 5 min ago
  • WarsawReachable78 ms, 5 min ago
  • St. LouisReachable231 ms, 5 min ago
  • JakartaReachable86 ms, 5 min ago
  • São PauloReachable32 ms, 5 min ago
  • Los AngelesReachable284 ms, 5 min ago
  • DallasReachable164 ms, 5 min ago
  • New YorkReachable37 ms, 5 min ago
  • SeoulReachable23 ms, 5 min ago
  • Hong KongReachable149 ms, 5 min ago
  • SingaporeReachable19 ms, 5 min ago
  • QuerétaroReachable243 ms, 5 min ago
  • HaminaReachable166 ms, 5 min ago
  • BangaloreReachable86 ms, 5 min ago
  • JohannesburgReachable29 ms, 5 min ago
  • PortsmouthReachable37 ms, 5 min ago
  • DohaReachable195 ms, 5 min ago
  • OsakaReachable52 ms, 5 min ago
  • LauterbourgReachable45 ms, 6 min ago

This is separate from the status page: we request github.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of GitHub Packages

GitHub
  • Git OperationsOperational
  • WebhooksOperational
  • Visit www.githubstatus.com for more informationOperational
  • API RequestsOperational
  • IssuesOperational
  • Pull RequestsOperational
  • ActionsOperational
  • PackagesOperational
  • PagesOperational
  • CopilotOperational
  • CodespacesOperational
  • Copilot AI Model ProvidersOperational

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

Last problem: 5 Nov, 23:39 UTC, partial outage for 43 min (Open incident: Degraded performance for multiple GitHub services).

Last 9030 days

91.09% of the time without a reported outage, since 2 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of github.com that failed (9,437 checks). Shaded: when GitHub Packages's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 00:0006:0012:0018:00 0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 102 checks failed0% of 107 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 99 checks failed0% of 111 checks failed0% of 88 checks failed0% of 103 checks failed0% of 101 checks failed0% of 105 checks failed0% of 97 checks failed0% of 79 checks failed0% of 80 checks failed0% of 109 checks failed0% of 91 checks failed0% of 108 checks failed0% of 99 checks failed0% of 94 checks failed0% of 79 checks failed0% of 87 checks failed0% of 95 checks failed0% of 103 checks failed0% of 83 checks failed0% of 84 checks failed0% of 84 checks failed0% of 88 checks failed0% of 92 checks failed0% of 79 checks failed0% of 79 checks failed0% of 87 checks failed0% of 81 checks failed0% of 79 checks failed0% of 86 checks failed0% of 74 checks failed0% of 71 checks failed0% of 90 checks failed0% of 89 checks failed0% of 106 checks failed0% of 89 checks failed0% of 85 checks failed0% of 103 checks failed0% of 104 checks failed0% of 98 checks failed0% of 74 checks failed0% of 85 checks failed0% of 96 checks failed0% of 84 checks failed0% of 103 checks failed0% of 105 checks failed0% of 79 checks failed

Recent problems

5 Nov, 23:39 UTCPartial outage43 minOpen incident: Degraded performance for multiple GitHub services
5 Nov, 16:53 UTCPartial outage50 minOpen incident: Incident with Actions
4 Nov, 17:41 UTCPartial outage36 minOpen incident: Incident with Actions
4 Nov, 16:06 UTCPartial outage58 minOpen incident: Incident with Actions and Pages
4 Nov, 08:47 UTCPartial outage3 h 4 minOpen incident: Incident with Pull Requests, Git Operations and Issues
3 Nov, 21:00 UTCPartial outage1 h 44 minOpen incident: Incident with Git Operations
3 Nov, 13:29 UTCPartial outage32 minOpen incident: Incident with API, Git, and Copilot requests
2 Nov, 17:48 UTCPartial outage39 minOpen incident: Elevated errors on GPT-5.4 Nano
What can I try?

Having trouble with GitHub Packages?

  1. Compare reports from Mongolia and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is GitHub Packages down, or is it just me?

The GitHub Packages status page reports no problem and our own checks reach github.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official GitHub Packages status page and load github.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in CI/CD

See the live outage feed for Mongolia · Find another service