User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fossa.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 361 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 198 ms | 0 |
| 03:15 | 0 | 0.0 | 371 ms | 0 |
| 03:30 | 0 | 0.0 | 656 ms | 0 |
| 03:45 | 0 | 0.0 | 924 ms | 0 |
| 04:00 | 0 | 0.0 | 338 ms | 0 |
| 04:15 | 0 | 0.0 | 350 ms | 0 |
| 04:30 | 0 | 0.0 | 205 ms | 0 |
| 04:45 | 0 | 0.0 | 399 ms | 0 |
| 05:00 | 0 | 0.0 | 185 ms | 0 |
| 05:15 | 0 | 0.0 | 1287 ms | 0 |
| 05:30 | 0 | 0.0 | 1512 ms | 0 |
| 05:45 | 0 | 0.0 | 231 ms | 0 |
| 06:00 | 0 | 0.0 | 1750 ms | 0 |
| 06:15 | 0 | 0.0 | 1184 ms | 0 |
| 06:30 | 0 | 0.0 | 357 ms | 0 |
| 06:45 | 0 | 0.0 | 987 ms | 0 |
| 07:00 | 0 | 0.0 | 1146 ms | 0 |
| 07:15 | 0 | 0.0 | 264 ms | 0 |
| 07:30 | 0 | 0.0 | 318 ms | 0 |
| 07:45 | 0 | 0.0 | 299 ms | 0 |
| 08:00 | 0 | 0.0 | 451 ms | 0 |
| 08:15 | 0 | 0.0 | 834 ms | 0 |
| 08:30 | 0 | 0.0 | 420 ms | 0 |
| 08:45 | 0 | 0.0 | 273 ms | 0 |
| 09:00 | 0 | 0.0 | 277 ms | 0 |
| 09:15 | 0 | 0.0 | 626 ms | 0 |
| 09:30 | 0 | 0.0 | 341 ms | 0 |
| 09:45 | 0 | 0.0 | 1575 ms | 0 |
| 10:00 | 0 | 0.0 | 615 ms | 0 |
| 10:15 | 0 | 0.0 | 236 ms | 0 |
| 10:30 | 0 | 0.0 | 1180 ms | 0 |
| 10:45 | 0 | 0.0 | 951 ms | 0 |
| 11:00 | 0 | 0.0 | 326 ms | 0 |
| 11:15 | 0 | 0.0 | 242 ms | 0 |
| 11:30 | 0 | 0.0 | 931 ms | 0 |
| 11:45 | 0 | 0.0 | 4006 ms | 0 |
| 12:00 | 0 | 0.0 | 198 ms | 0 |
| 12:15 | 0 | 0.0 | 795 ms | 0 |
| 12:30 | 0 | 0.0 | 249 ms | 0 |
| 12:45 | 0 | 0.0 | 284 ms | 0 |
| 13:00 | 0 | 0.0 | 314 ms | 0 |
| 13:15 | 0 | 0.0 | 424 ms | 0 |
| 13:30 | 0 | 0.0 | 361 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for FOSSA yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when FOSSA goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FOSSA alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If FOSSA is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on FOSSA's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.