InEvent logo

Is InEvent Down?

SaaSLive status, outages, and incident history

No. InEvent is up right now.

Every monitored InEvent system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment InEvent breaks

InEvent is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official InEvent status page
How we know: the official InEvent status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

InEvent Status Summary

As of 18:13 UTC on 14 November 2026, InEvent is operational. PulsAPI checked InEvent's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "Emergency security maintenance – PHP security update "PHP2Shell"", was on Oct 21, 2026 and lasted 23h 31m.

Cite as: PulsAPI, “InEvent status”, checked 14 November 2026, 18:13 UTC. https://www.pulsapi.com/services/inevent

InEvent Component Status

The main InEvent systems on this page. All 8 are operational right now.

8operational
API
Operational
Cloudflare CDN/Cache
Operational
Firebase Web Sockets
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Live Stream CDNs » AWS Interactive Video Service, Live Stream CDNs » Mux Streaming Service, Platform, Postmark Email Service, UK Server Region.

See all of them free

Component statuses may change independently during partial outages.

Recent InEvent Outages & Incidents

Incident history from the official InEvent status page, including resolution updates.

Emergency security maintenance – PHP security update "PHP2Shell"Resolved Oct 21, 2026 · 23h 31mResolved

This incident has been resolved. --- [2026-10-21T09:52:53.172-04:00] (identified) The fix is currently being applied and we shall resume shortly. --- [2026-10-21T09:42:43.363-04:00] (identified) On Wednesday, October 21, at 10:00 AM EDT (14:00 UTC), we will apply an emergency security update to our servers. The PHP project is releasing fixes today for two critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619). These are remote code execution flaws in PHP itself, rated 9.2 on the CVSS v4.0 scale. PHP powers roughly 7 in 10 websites, and the issue is being treated as an industry-wide emergency. We are applying the update as soon as it is released to keep the InEvent platform and your data secure. What to expect: to apply the patch safely, we may put the platform into maintenance mode until the update is complete. During this time, the InEvent platform, API, event pages and apps may be temporarily unavailable or slower than usual. Events running during this window may be affected. We’ll keep the maintenance window as short as possible and post updates here as work progresses. Subscribe to this page for notifications. If you have an event running today and need help, contact our support team. For more information about the PHP security release, visit php.net.

Bi-weekly digest emails sent repeatedlyResolved Sep 30, 2026 · 10 minResolved

This issue is resolved. We found and fixed a code issue that caused the automated bi-weekly digest email to be sent more often than scheduled. Digest emails are back on their normal schedule. No other emails or platform features were affected. If you received extra digest emails, you can delete them, and you don't need to do anything on your account. We're sorry for the inconvenience. --- [2026-09-30T11:33:28.879-04:00] (investigating) We're looking into reports that some admins are getting the automated bi-weekly digest email more often than scheduled. Only the digest email is affected. All other emails and platform features are working normally. You can delete any extra digest emails, and you don't need to do anything on your account. We'll post another update as soon as we have more information.

InEvent Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a InEvent incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live InEvent Outage Reports

Problems reported by engineers using InEvent. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No InEvent problems reported yet.

Something wrong with InEvent on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About InEvent

InEvent posts its status at trust.inevent.com. The page covers 8 components, among them API, Cloudflare CDN/Cache and Firebase Web Sockets. Past incidents and uptime for InEvent stay on this page, which helps when you want to know how often it has trouble.

InEvent Status FAQ

Is InEvent down right now?

The verdict at the top of this page comes from the latest poll of the official InEvent status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if InEvent is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until InEvent recovers.

How do I check InEvent uptime history?

PulsAPI tracks InEvent uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever InEvent changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect InEvent outages?

PulsAPI reads the official InEvent status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual InEvent components?

Yes. PulsAPI monitors 8 individual InEvent components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when InEvent goes down?

Yes. Create a free account and subscribe to InEvent: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with InEvent to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot InEvent problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor InEvent?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so InEvent plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track InEvent with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services