User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
codefresh.io · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests codefresh.io from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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 1464 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 936 ms | 0 |
| 03:15 | 0 | 0.0 | 910 ms | 0 |
| 03:30 | 0 | 0.0 | 2439 ms | 0 |
| 03:45 | 0 | 0.0 | 558 ms | 0 |
| 04:00 | 0 | 0.0 | 2216 ms | 0 |
| 04:15 | 0 | 0.0 | 3100 ms | 0 |
| 04:30 | 0 | 0.0 | 648 ms | 0 |
| 04:45 | 0 | 0.0 | 1930 ms | 0 |
| 05:00 | 0 | 0.0 | 2104 ms | 0 |
| 05:15 | 0 | 0.0 | 1103 ms | 0 |
| 05:30 | 0 | 0.0 | 1145 ms | 0 |
| 05:45 | 0 | 0.0 | 603 ms | 0 |
| 06:00 | 0 | 0.0 | 1645 ms | 0 |
| 06:15 | 0 | 0.0 | 1088 ms | 0 |
| 06:30 | 0 | 0.0 | 482 ms | 0 |
| 06:45 | 0 | 0.0 | 901 ms | 0 |
| 07:00 | 0 | 0.0 | 1708 ms | 0 |
| 07:15 | 0 | 0.0 | 637 ms | 0 |
| 07:30 | 0 | 0.0 | 1014 ms | 0 |
| 07:45 | 0 | 0.0 | 1265 ms | 0 |
| 08:00 | 0 | 0.0 | 1596 ms | 0 |
| 08:15 | 0 | 0.0 | 2149 ms | 0 |
| 08:30 | 0 | 0.0 | 1990 ms | 0 |
| 08:45 | 0 | 0.0 | 3066 ms | 0 |
| 09:00 | 0 | 0.0 | 1821 ms | 0 |
| 09:15 | 0 | 0.0 | 834 ms | 0 |
| 09:30 | 0 | 0.0 | 541 ms | 0 |
| 09:45 | 0 | 0.0 | 1277 ms | 0 |
| 10:00 | 0 | 0.0 | 828 ms | 0 |
| 10:15 | 0 | 0.0 | 659 ms | 0 |
| 10:30 | 0 | 0.0 | 1150 ms | 0 |
| 10:45 | 0 | 0.0 | 669 ms | 0 |
| 11:00 | 0 | 0.0 | 1638 ms | 0 |
| 11:15 | 0 | 0.0 | 871 ms | 0 |
| 11:30 | 0 | 0.0 | 1050 ms | 0 |
| 11:45 | 0 | 0.0 | 569 ms | 0 |
| 12:00 | 0 | 0.0 | 1183 ms | 0 |
| 12:15 | 0 | 0.0 | 865 ms | 0 |
| 12:30 | 0 | 0.0 | 1877 ms | 0 |
| 12:45 | 0 | 0.0 | 750 ms | 0 |
| 13:00 | 0 | 0.0 | 1738 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 Codefresh 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 Codefresh goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Codefresh 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 Codefresh 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 Codefresh'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.