User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
codesignal.com · Cloud & developer
Is CodeSignal down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → codesignal.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 245 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 233 ms | 0 |
| Mon 14 | 0 | 0.0 | 224 ms | 0 |
| Mon 16 | 0 | 0.0 | 245 ms | 0 |
| Mon 18 | 0 | 0.0 | 263 ms | 0 |
| Mon 20 | 0 | 0.0 | 345 ms | 0 |
| Mon 22 | 0 | 0.0 | 270 ms | 0 |
| Tue 00 | 0 | 0.0 | 379 ms | 0 |
| Tue 03 | 0 | 0.0 | 264 ms | 0 |
| Tue 05 | 0 | 0.0 | 88 ms | 0 |
| Tue 07 | 0 | 0.0 | 184 ms | 0 |
| Tue 09 | 0 | 0.0 | 314 ms | 0 |
| Tue 11 | 0 | 0.0 | 328 ms | 0 |
| Tue 13 | 0 | 0.0 | 302 ms | 0 |
| Tue 15 | 0 | 0.0 | 409 ms | 0 |
| Tue 18 | 0 | 0.0 | 173 ms | 0 |
| Tue 20 | 0 | 0.0 | 263 ms | 0 |
| Tue 22 | 0 | 0.0 | 287 ms | 0 |
| Wed 00 | 0 | 0.0 | 257 ms | 0 |
| Wed 03 | 0 | 0.0 | 260 ms | 0 |
| Wed 05 | 0 | 0.0 | 273 ms | 0 |
| Wed 07 | 0 | 0.0 | 165 ms | 0 |
| Wed 09 | 0 | 0.0 | 162 ms | 0 |
| Wed 12 | 0 | 0.0 | 274 ms | 0 |
| Wed 14 | 0 | 0.0 | 219 ms | 0 |
| Wed 16 | 0 | 0.0 | 232 ms | 0 |
| Wed 18 | 0 | 0.0 | 362 ms | 0 |
| Wed 20 | 0 | 0.0 | 290 ms | 0 |
| Wed 22 | 0 | 0.0 | 363 ms | 0 |
| Thu 01 | 0 | 0.0 | 190 ms | 0 |
| Thu 03 | 0 | 0.0 | 363 ms | 0 |
| Thu 05 | 0 | 0.0 | 213 ms | 0 |
| Thu 07 | 0 | 0.0 | 320 ms | 0 |
| Thu 09 | 0 | 0.0 | 376 ms | 0 |
| Thu 11 | 0 | 0.0 | 217 ms | 0 |
| Thu 13 | 0 | 0.0 | 219 ms | 0 |
| Thu 15 | 0 | 0.0 | 320 ms | 0 |
| Thu 16 | 0 | 0.0 | 430 ms | 0 |
| Thu 19 | 0 | 0.0 | 250 ms | 0 |
| Thu 21 | 0 | 0.0 | 163 ms | 0 |
| Thu 22 | 0 | 0.0 | 159 ms | 0 |
| Fri 01 | 0 | 0.0 | 163 ms | 0 |
| Fri 03 | 0 | 0.0 | 171 ms | 0 |
| Fri 05 | 0 | 0.0 | 268 ms | 0 |
| Fri 07 | 0 | 0.0 | 348 ms | 0 |
| Fri 09 | 0 | 0.0 | 188 ms | 0 |
| Fri 11 | 0 | 0.0 | 363 ms | 0 |
| Fri 13 | 0 | 0.0 | 250 ms | 0 |
| Fri 15 | 0 | 0.0 | 245 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live CodeSignal badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for CodeSignal yet. Outages of 10 minutes or more get their own page here.
Having trouble with CodeSignal?
One report per service every 10 minutes from this network. No account.
Follow CodeSignal
Get an email when CodeSignal goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CodeSignal alerts to Slack, Discord or a webhook — free.
About CodeSignal
CodeSignal, at codesignal.com, is one of the Cloud & developer services we monitor. Discover the agentic skills intelligence platform that helps teams see, measure, develop, and grow skills clearly with confidence.
CodeSignal publishes an official status page at status.codesignal.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 243 ms average, 150–430 ms range across 13 successful checks.
Questions
Is CodeSignal down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was CodeSignal last down?
We have not recorded a public CodeSignal incident since monitoring began 8 days ago.
What is CodeSignal's uptime?
From our own checks: 100% over 8 days of checks.
How fast does CodeSignal respond?
243 ms on average over the last 24 hours (150–430 ms).
Does CodeSignal have an official status page?
Yes, at https://status.codesignal.com.
CodeSignal not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report CodeSignal here at once, the problem is on CodeSignal's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with CodeSignal. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.