User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 90 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 01 | 0 | 0.0 | 180 ms | 0 |
| Wed 03 | 0 | 0.0 | 195 ms | 0 |
| Wed 05 | 0 | 0.0 | 74 ms | 0 |
| Wed 08 | 0 | 0.0 | 101 ms | 0 |
| Wed 10 | 0 | 0.0 | 62 ms | 0 |
| Wed 12 | 0 | 0.0 | 213 ms | 0 |
| Wed 14 | 0 | 0.0 | 50 ms | 0 |
| Wed 16 | 0 | 0.0 | 112 ms | 0 |
| Wed 18 | 0 | 0.0 | 215 ms | 0 |
| Wed 21 | 0 | 0.0 | 49 ms | 0 |
| Wed 23 | 0 | 0.0 | 62 ms | 0 |
| Thu 01 | 0 | 0.0 | 93 ms | 0 |
| Thu 03 | 0 | 0.0 | 65 ms | 0 |
| Thu 05 | 0 | 0.0 | 87 ms | 0 |
| Thu 07 | 0 | 0.0 | 51 ms | 0 |
| Thu 09 | 0 | 0.0 | 139 ms | 0 |
| Thu 11 | 0 | 0.0 | 70 ms | 0 |
| Thu 13 | 0 | 0.0 | 240 ms | 0 |
| Thu 15 | 0 | 0.0 | 133 ms | 0 |
| Thu 18 | 0 | 0.0 | 100 ms | 0 |
| Thu 20 | 0 | 0.0 | 90 ms | 0 |
| Thu 22 | 0 | 0.0 | 108 ms | 0 |
| Fri 00 | 0 | 0.0 | 187 ms | 0 |
| Fri 01 | 0 | 0.0 | 123 ms | 0 |
| Fri 03 | 0 | 0.0 | 152 ms | 0 |
| Fri 05 | 0 | 0.0 | 72 ms | 0 |
| Fri 07 | 0 | 0.0 | 74 ms | 0 |
| Fri 10 | 0 | 0.0 | 63 ms | 0 |
| Fri 11 | 0 | 0.0 | 248 ms | 0 |
| Fri 12 | 0 | 0.0 | 28 ms | 0 |
| Fri 14 | 0 | 0.0 | 109 ms | 0 |
| Fri 16 | 0 | 0.0 | 102 ms | 0 |
| Fri 18 | 0 | 0.0 | 52 ms | 0 |
| Fri 20 | 0 | 0.0 | 225 ms | 0 |
| Fri 22 | 0 | 0.0 | 119 ms | 0 |
| Sat 00 | 0 | 0.0 | 186 ms | 0 |
| Sat 02 | 0 | 0.0 | 95 ms | 0 |
| Sat 04 | 0 | 0.0 | 193 ms | 0 |
| Sat 06 | 0 | 0.0 | 99 ms | 0 |
| Sat 08 | 0 | 0.0 | 74 ms | 0 |
| Sat 10 | 0 | 0.0 | 257 ms | 0 |
| Sat 13 | 0 | 0.0 | 197 ms | 0 |
| Sat 15 | 0 | 0.0 | 205 ms | 0 |
| Sat 17 | 0 | 0.0 | 65 ms | 0 |
| Sat 20 | 0 | 0.0 | 269 ms | 0 |
| Sat 22 | 0 | 0.0 | 71 ms | 0 |
| Sun 00 | 0 | 0.0 | 196 ms | 0 |
| Sun 03 | 0 | 0.0 | 90 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Immune Epitope Database 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 Immune Epitope Database goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Immune Epitope Database is listed in our Cloud & developer category and checked at iedb.org. Free resource for searching and exporting immune epitopes. Includes more than 95% of all published infectious disease, allergy, autoimmune, and transplant epitope data.
Immune Epitope Database publishes an official status page at status.iedb.org; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 156 ms average, 49–326 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Immune Epitope Database incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
156 ms on average over the last 24 hours (49–326 ms).
Yes, at https://status.iedb.org.
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 Immune Epitope Database here at once, the problem is on Immune Epitope Database'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 Immune Epitope Database. 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.