User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Grip 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 → grip.events—
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 10 min ago. Last stored result reached it in 41 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 |
|---|---|---|---|---|
| 06:30 | 0 | 0.0 | 58 ms | 0 |
| 08:30 | 0 | 0.0 | 36 ms | 0 |
| 10:30 | 0 | 0.0 | 48 ms | 0 |
| 12:45 | 0 | 0.0 | 101 ms | 0 |
| 14:45 | 0 | 0.0 | 131 ms | 0 |
| 16:45 | 0 | 0.0 | 112 ms | 0 |
| 19:00 | 0 | 0.0 | 67 ms | 0 |
| 21:00 | 0 | 0.0 | 108 ms | 0 |
| 23:00 | 0 | 0.0 | 74 ms | 0 |
| 01:00 | 0 | 0.0 | 97 ms | 0 |
| 03:15 | 0 | 0.0 | 64 ms | 0 |
| 05:15 | 0 | 0.0 | 41 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 Grip 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 Grip yet. Outages of 10 minutes or more get their own page here.
Having trouble with Grip?
One report per service every 10 minutes from this network. No account.
Follow Grip
Get an email when Grip goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Grip alerts to Slack, Discord or a webhook — free.
About Grip
Grip, at grip.events, is one of the AI services we monitor. Grip is the AI-powered event platform for networking, matchmaking, and lead generation. Trusted by SXSW, Money20/20, and Clarion Events to connect thousands of participants.
Grip publishes an official status page at status.grip.events; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 78 ms average, 36–131 ms range across 12 successful checks.
Questions
Is Grip down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Grip last down?
We have not recorded a public Grip incident since monitoring began 8 days ago.
What is Grip's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Grip respond?
78 ms on average over the last 24 hours (36–131 ms).
Does Grip have an official status page?
Yes, at https://status.grip.events.
Grip 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 Grip here at once, the problem is on Grip'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 Grip. 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.