Last checked 11/5/2026, 5:18:37 AM. Core pages are checked hourly; other components are sampled each run rather than checked exhaustively every time — see this page's own source for the full explanation.
Known issues
No elevated error activity in the last hour.
Components
Career MapOperational
Learning resources(4 of 36 outbound links unreachable)Operational
CritiqueOperational
DiscussionsOperational
EventsOperational
Job listings(70 of 679 outbound links unreachable)Operational
Learning PathsOperational
Mentor profilesOperational
NewsOperational
PodcastsOperational
Core pagesOperational
ProjectsOperational
Skill LabsOperational
Community & social links(39 of 85 outbound links unreachable)Operational
Services
Whether each service this site depends on answers right now — a live ping, not inferred from whether a page happened to load.
Monitoring databaseOperational
Mentor requests databaseOperational
Member goals databaseOperational
Member accounts APIOperational
Database
The database cluster, one row per node, measured from inside the database every ten minutes. Streaming says whether a replica is receiving changes from the primary; Behind says how much it has not yet applied, in data and in time. Cache is ticked where the query cache served correctly in that location this run. A replica is marked degraded once it is more than 30 seconds behind. A problem in one zone shows on that zone's row rather than as the whole database.
Location
Role
Zone
Streaming
Behind (data)
Behind (time)
Cache
Status
🇺🇸Virginia
Primary
us-east-1b
9 of 9 replicas
—
—
—
Operational
🇺🇸Virginia
Replica
us-east-1a
✓
0 KiB
0.0 s
✓
Operational
🇺🇸Virginia
Replica
us-east-1c
✓
0 KiB
0.0 s
✓
Operational
🇺🇸Oregon
Replica
us-west-2c
✓
0 KiB
0.0 s
✓
Operational
🇧🇷São Paulo
Replica
sa-east-1b
✓
0 KiB
0.0 s
✓
Operational
🇮🇳Mumbai
Replica
ap-south-1a
✓
0 KiB
0.0 s
✓
Operational
🇩🇪Frankfurt
Replica
eu-central-1b
✓
0 KiB
0.0 s
✓
Operational
🇦🇺Sydney
Replica
ap-southeast-2c
✓
0 KiB
0.0 s
✓
Operational
🇯🇵Tokyo
Replica
ap-northeast-1d
✓
0 KiB
0.0 s
✓
Operational
🇸🇬Singapore
Replica
ap-southeast-1c
✓
0 KiB
0.0 s
✓
Operational
Reads around the world
Every 5 minutes, probes in three hundred cities on six continents make a real database read through the API. Each is routed to its nearest region — Virginia, Oregon, São Paulo, Mumbai, Frankfurt, Singapore, Sydney or Tokyo — and the API reports which database actually answered, how long a cached read took, and how long a read that went all the way to the database took.A slow read is usually distance from the nearest replica, not a fault. A red row is a city answered by the wrong database. The cache hit is a single sample and mostly connection setup, so it is not graded.192 of 192 cities read from the region they were routed to, measured 3 minutes ago; 1 probes did not reach the API.
Each city is a dot in its database read's speed band, joined by a line to the region that answered it. A city not answered by its own region is red, with no line. Hover a dot for its time. Measured 3 minutes ago.
Region
Fast · 50 ms or less
Normal · 51–150 ms
Far from a replica · over 150 ms
Not answered by its own region
Hover or tap a region to see the cities it serves.
Automatic routing
Each data center reads from the region a table in code gives it. The API corrects that on its own: a data center moves to another region only when three days of timings from real traffic show it clearly faster, and a region that stops answering is taken out until it recovers. Writes always go to the primary in Virginia.
Every region is answering, and every data center reads from the region the table gives it.
No automatic changes yet.
This page reflects automated checks only — a component reading "Operational" means our own monitoring hasn't detected a problem, not a guarantee nothing is wrong. Some external sites reject automated requests outright regardless of whether they're actually up for a real visitor; see our own engineering notes if a status here looks surprising.