Is GitHub Packages down in Lebanon?
No problems reported with GitHub Packages right now
Reports from people in Lebanon
Last 24 hours · Lebanon · times in UTC
No community reports in the last 24 hours from Lebanon. Having trouble? Add your report.
Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.
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.
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 Lebanon. The report chart above is filtered to Lebanon.
Our own checks of github.com
Every 5 minutes, from our probesOur checks from 35 cities: all fine.
- AmsterdamReachable42 ms, just now
- QuerétaroReachable241 ms, 2 min ago
- MadridReachable118 ms, 3 min ago
- St. LouisReachable154 ms, 3 min ago
- DelhiReachable126 ms, 3 min ago
- DohaReachable196 ms, 3 min ago
- MelbourneReachable71 ms, 4 min ago
- São PauloReachable76 ms, 4 min ago
- Tel AvivReachable32 ms, 4 min ago
- DallasReachable164 ms, 4 min ago
- Los AngelesReachable290 ms, 4 min ago
- Hong KongReachable153 ms, 4 min ago
- New YorkReachable40 ms, 4 min ago
- BangaloreReachable99 ms, 4 min ago
- SeoulReachable19 ms, 4 min ago
- SingaporeReachable18 ms, 4 min ago
- Cape TownReachable130 ms, 4 min ago
- LauterbourgReachable1295 ms, 4 min ago
- SeattleReachable46 ms, 4 min ago
- FrankfurtReachable11 ms, 4 min ago
- AtlantaReachable72 ms, 5 min ago
- JohannesburgReachable190 ms, 5 min ago
- TorontoReachable100 ms, 5 min ago
- MumbaiReachable304 ms, 5 min ago
- SydneyReachable68 ms, 6 min ago
- TokyoReachable81 ms, 6 min ago
- LondonReachable24 ms, 6 min ago
- SantiagoReachable211 ms, 8 min ago
- Port LouisReachable236 ms, 8 min ago
- PortsmouthReachable28 ms, 9 min ago
- New JerseyReachable2599 ms, 9 min ago
- HaminaReachable152 ms, 9 min ago
- OsakaReachable47 ms, 10 min ago
- JakartaReachable83 ms, 13 min ago
- WarsawReachable77 ms, 13 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
90.80% of the time without a reported outage, since 2 NovOf 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.
No problems Partial outage Major outage Maintenance No data yet
Last 24 hours
Every 15 minutes, hours in UTCBars: the share of our own checks of github.com that failed (9,481 checks). Shaded: when GitHub Packages's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.
Recent problems
| 5 Nov, 23:39 UTC | Partial outage | 43 min | Open incident: Degraded performance for multiple GitHub services |
| 5 Nov, 16:53 UTC | Partial outage | 50 min | Open incident: Incident with Actions |
| 4 Nov, 17:41 UTC | Partial outage | 36 min | Open incident: Incident with Actions |
| 4 Nov, 16:06 UTC | Partial outage | 58 min | Open incident: Incident with Actions and Pages |
| 4 Nov, 08:47 UTC | Partial outage | 3 h 4 min | Open incident: Incident with Pull Requests, Git Operations and Issues |
| 3 Nov, 21:00 UTC | Partial outage | 1 h 44 min | Open incident: Incident with Git Operations |
| 3 Nov, 13:29 UTC | Partial outage | 32 min | Open incident: Incident with API, Git, and Copilot requests |
| 2 Nov, 17:48 UTC | Partial outage | 39 min | Open incident: Elevated errors on GPT-5.4 Nano |
What can I try?
Having trouble with GitHub Packages?
- Compare reports from Lebanon and check the latest update above. A quiet chart does not rule out a new or local problem.
- Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
- 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
BuildJetCI/CDMajor outage2 of 3 parts affected: Current status by service / Dashboard, Current status by service…View statusReport a problem
BitriseCI/CDPartial outageOpen incident: Interrupted builds and longer queue timesView statusReport a problem- QoveryCI/CDPartial outage3 of 74 parts affected: Customer infrastructure: Scaleway / Third Party: Scaleway →…View statusReport a problem