FROM ALL SOURCES
Gcore's status page shows “Maintenance”. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: normal.
- Vendor status page Maintenance
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS199524 prefixes seen by 100% of RIPE RIS peers
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | not seen | n/a |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 15 h 6 min |
Evidence
- Official page: Maintenance (“UNDERMAINTENANCE”). evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- AS199524 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium
What we don't know: what is happening inside Gcore's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor shows Maintenance with no open incident stage. Outside signals: users: normal · routing: normal. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Gcore. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Gcore, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; routing visibility returning to normal; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Gcore. No blame or attack claims without an official source. Generated .