Uptime reports

20 services developers depend on, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Each report has the state now, availability from a day to a year, response time by location and every outage, dated in UTC.

statoss.com/uptimeEvery 5 minutes

Service24 hours30 daysOutages

Code and packages

GitHubUp99.65%Too new0
GitLabUp100%Too new0
npm registryUp100%Too new0
PyPIUp100%Too new0
Docker HubUp100%Too new0

Hosting and edge

CloudflareUp100%Too new0
VercelUp100%Too new0
NetlifyUp99.65%Too new0
Fly.ioUp100%Too new0
RenderUp100%Too new0

Cloud

AWS (DynamoDB, us-east-1)Up100%Too new0
Google CloudUp100%Too new0

Payments and messaging

Stripe APIUp100%Too new0
Twilio APIUp100%Too new0

Chat

SlackUp100%Too new0
DiscordUp100%Too new0

AI APIs

OpenAI APIUp100%Too new0
Anthropic APIUp100%Too new0

Developer platforms

SentryUp100%Too new1
SupabaseUp100%Too new0

The dot is the state now: green up, red down, grey not checked yet. The percentages are the share of checks that passed; outages are those that began in the last 90 days. As of 2026-10-06 11:02 UTC.

How the reports are made

Every service is a monitor on a StatOSS status page of our own, checked every 5 minutes from one location at a time, in turn: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. A failed check is repeated from a second location and counts only when that one fails too. Two failed checks in a row make an outage; the first check that passes ends it. A year of history is kept.

Each target is a public address that answers without credentials, requested once per interval with a plain GET. Where a service has no such address that answers 200, the check expects the status an unauthenticated request gets, 401 or 403: the service's API answered, and turned the request away as it should. Each report says what is checked and what that leaves out.

The services

GitHub uptime: GET api.github.com/rate_limit, up on status 200. Git hosting, pull requests, issues, Actions and packages. Most open source code and a large share of private code lives there.
GitLab uptime: GET gitlab.com/api/v4/version, up on status 401. GitLab.com, the hosted GitLab: Git repositories, merge requests, CI/CD pipelines and a package and container registry.
npm registry uptime: GET registry.npmjs.org/-/ping, up on status 200. The public registry behind npm, pnpm, Yarn and Bun installs: package metadata and tarballs for JavaScript and TypeScript.
PyPI uptime: GET pypi.org/simple/pip/, up on status 200. The Python Package Index, where pip, uv and Poetry find and download Python packages.
Docker Hub uptime: GET registry-1.docker.io/v2/, up on status 401. Docker's public container registry, where `docker pull` looks for images that name no other registry.
Cloudflare uptime: GET api.cloudflare.com/client/v4/ips, up on status 200. CDN, DNS, DDoS protection, Workers and a large part of the web's front doors. StatOSS itself sits behind it.
Vercel uptime: GET api.vercel.com/v2/user, up on status 403. Hosting for front ends and Next.js apps, with builds, serverless and edge functions.
Netlify uptime: GET api.netlify.com/api/v1/sites, up on status 401. Hosting for static sites and front ends, with builds, functions and forms.
Fly.io uptime: GET api.machines.dev/v1/apps, up on status 401. Runs apps as Firecracker machines in regions around the world. One of StatOSS's own check locations runs there.
Render uptime: GET api.render.com/v1/services, up on status 401. Hosting for web services, workers, cron jobs and Postgres, deployed from a Git repository.
AWS (DynamoDB, us-east-1) uptime: GET dynamodb.us-east-1.amazonaws.com, up on status 200 with the text healthy in the body. Amazon Web Services. us-east-1, in Northern Virginia, is its oldest and largest region, and the default in many SDKs and tutorials.
Google Cloud uptime: GET cloudresourcemanager.googleapis.com/v1/projects, up on status 401. Google's cloud: Compute Engine, Cloud Run, GKE, Cloud Storage, BigQuery and the APIs behind them.
Stripe API uptime: GET api.stripe.com/v1/charges, up on status 401. Online payments, subscriptions and invoices, used by a large share of the web's checkouts.
Twilio API uptime: GET api.twilio.com/2010-04-01/Accounts.json, up on status 401. APIs for SMS, voice calls, WhatsApp and phone verification.
Slack uptime: GET slack.com/api/api.test, up on status 200 with the text "ok":true in the body. Team chat, and the place many teams send their alerts, deploy notices and bot messages.
Discord uptime: GET discord.com/api/v10/gateway, up on status 200. Voice, video and text chat, home to many open source and gaming communities and their bots.
OpenAI API uptime: GET api.openai.com/v1/models, up on status 401. The API behind GPT models, used by apps that call a language model, generate images or transcribe audio.
Anthropic API uptime: GET api.anthropic.com/v1/models, up on status 401. The API behind Claude models, used by apps and coding tools that call Claude.
Sentry uptime: GET sentry.io/api/0/, up on status 200. Error tracking and performance monitoring: SDKs in apps send errors and traces there.
Supabase uptime: GET api.supabase.com/v1/projects, up on status 401. Hosted Postgres with authentication, storage, realtime and edge functions around it.