User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Interprefy 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 → interprefy.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 2 hr ago. Last stored result reached it in 72 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 14 | 0 | 0.0 | 67 ms | 0 |
| Mon 16 | 0 | 0.0 | 94 ms | 0 |
| Mon 18 | 0 | 0.0 | 84 ms | 0 |
| Mon 20 | 0 | 0.0 | 90 ms | 0 |
| Mon 22 | 0 | 0.0 | 30 ms | 0 |
| Tue 00 | 0 | 0.0 | 102 ms | 0 |
| Tue 02 | 0 | 0.0 | 79 ms | 0 |
| Tue 04 | 0 | 0.0 | 236 ms | 0 |
| Tue 06 | 0 | 0.0 | 103 ms | 0 |
| Tue 09 | 0 | 0.0 | 100 ms | 0 |
| Tue 11 | 0 | 0.0 | 243 ms | 0 |
| Tue 13 | 0 | 0.0 | 153 ms | 0 |
| Tue 15 | 0 | 0.0 | 123 ms | 0 |
| Tue 17 | 0 | 0.0 | 77 ms | 0 |
| Tue 20 | 0 | 0.0 | 121 ms | 0 |
| Tue 22 | 0 | 0.0 | 50 ms | 0 |
| Wed 00 | 0 | 0.0 | 104 ms | 0 |
| Wed 02 | 0 | 0.0 | 54 ms | 0 |
| Wed 05 | 0 | 0.0 | 102 ms | 0 |
| Wed 07 | 0 | 0.0 | 96 ms | 0 |
| Wed 09 | 0 | 0.0 | 70 ms | 0 |
| Wed 11 | 0 | 0.0 | 75 ms | 0 |
| Wed 13 | 0 | 0.0 | 93 ms | 0 |
| Wed 15 | 0 | 0.0 | 76 ms | 0 |
| Wed 18 | 0 | 0.0 | 107 ms | 0 |
| Wed 20 | 0 | 0.0 | 167 ms | 0 |
| Wed 22 | 0 | 0.0 | 118 ms | 0 |
| Thu 00 | 0 | 0.0 | 130 ms | 0 |
| Thu 02 | 0 | 0.0 | 133 ms | 0 |
| Thu 04 | 0 | 0.0 | 85 ms | 0 |
| Thu 06 | 0 | 0.0 | 105 ms | 0 |
| Thu 08 | 0 | 0.0 | 78 ms | 0 |
| Thu 11 | 0 | 0.0 | 96 ms | 0 |
| Thu 13 | 0 | 0.0 | 99 ms | 0 |
| Thu 15 | 0 | 0.0 | 53 ms | 0 |
| Thu 17 | 0 | 0.0 | 61 ms | 0 |
| Thu 18 | 0 | 0.0 | 68 ms | 0 |
| Thu 20 | 0 | 0.0 | 78 ms | 0 |
| Thu 22 | 0 | 0.0 | 248 ms | 0 |
| Fri 00 | 0 | 0.0 | 121 ms | 0 |
| Fri 02 | 0 | 0.0 | 68 ms | 0 |
| Fri 04 | 0 | 0.0 | 149 ms | 0 |
| Fri 06 | 0 | 0.0 | 118 ms | 0 |
| Fri 08 | 0 | 0.0 | 95 ms | 0 |
| Fri 10 | 0 | 0.0 | 70 ms | 0 |
| Fri 12 | 0 | 0.0 | 73 ms | 0 |
| Fri 14 | 0 | 0.0 | 95 ms | 0 |
| Fri 16 | 0 | 0.0 | 72 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Interprefy 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 Interprefy yet. Outages of 10 minutes or more get their own page here.
Having trouble with Interprefy?
One report per service every 10 minutes from this network. No account.
Follow Interprefy
Get an email when Interprefy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Interprefy alerts to Slack, Discord or a webhook — free.
About Interprefy
Interprefy, at interprefy.com, is one of the AI services we monitor. Empower your multilingual events with Interprefy interpretation, AI speech translation, and captions, ensuring seamless communication for global audiences.
Interprefy publishes an official status page at status.interprefy.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 105 ms average, 68–248 ms range across 12 successful checks.
Questions
Is Interprefy down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Interprefy last down?
We have not recorded a public Interprefy incident since monitoring began 6 days ago.
What is Interprefy's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Interprefy respond?
105 ms on average over the last 24 hours (68–248 ms).
Does Interprefy have an official status page?
Yes, at https://status.interprefy.com.
Interprefy 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Interprefy here at once, the problem is on Interprefy'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 Interprefy. 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.