amazee.io logo

Is amazee.io Down?

Cloud InfrastructureLive status, outages, and incident history

No. amazee.io is up right now.

Every monitored amazee.io 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 amazee.io breaks

amazee.io 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.

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

Status report

amazee.io Status Summary

As of 16:47 UTC on 14 November 2026, amazee.io is operational. PulsAPI checked amazee.io's official status page and found 29 of 29 components operational, with no active incidents. The latest incident, "Notice: Webhook Signature Verification", started on Nov 2, 2026 and is still open.

Cite as: PulsAPI, “amazee.io status”, checked 14 November 2026, 16:47 UTC. https://www.pulsapi.com/services/amazee-io

amazee.io Component Status

The main amazee.io systems on this page. All 29 are operational right now.

29operational
Australia » amazee.ai infrastructure: au103
Operational
Australia » au2.lagoon
Operational
Canada » ca1.lagoon
Operational

26 more components tracked

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

Also tracking Dedicated » amazee.ai infrastructure, Dedicated » AMER, Dedicated » APAC, Dedicated » EMEA, Dedicated » Japan, Finland » fi2.lagoon, General » CDN, General » Deployment Infrastructure, General » Lagoon API, General » Lagoon Dashboard, General » Lagoon Logs, General » my.amazee.io, and 14 more.

See all of them free

Component statuses may change independently during partial outages.

Recent amazee.io Outages & Incidents

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

Notice: Webhook Signature VerificationStarted Nov 2, 2026Investigating

Lagoon is enforcing signature verification on all incoming webhooks to ensure that only authenticated requests from your Git provider trigger automatic actions. * What is affected: Automatic actions triggered via Git webhooks will be paused for repositories until the webhook token secret is configured. * What is unaffected: Live environments, cron jobs, backups, and site data are completely unaffected (no downtime). Manual deployments via the Lagoon UI and Lagoon-cli remain functional. Required action: visit https://updates.amazee.io/posts/lagoon-secure-webhook-tokens/ for instructions on how to update your webhook configuration.

CVE-2026-98432Started Oct 30, 2026Investigating

We are currently still in progress patching all of our clusters and will advise once completed --- [2026-11-02T00:43:55.522Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-30T06:11:29.439Z] (identified) We are aware of the recently disclosed Linux kernel vulnerability CVE-2026-98432 and will perform emergency maintenance to apply the updates required. The work will take place during the same hours as regular maintenance but tonight or over the weekend instead of on the normal day. During the maintenance, your sites may experience minor disruption to service

Regular Maintenance - amazee.ai InfrastructureResolved Oct 27, 2026 · 18 minResolved

This incident has been resolved. --- [2026-10-27T18:22:58.350Z] (monitoring) We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

Upcoming maintenance

Announced by amazee.io. Planned work, not an outage.

Regular Cloud Maintenance - AMERICASScheduled for Nov 17, 2026 · 5h 0mScheduled

We are conducting regular maintenance on our systems. This can lead to short interruptions for connections with the dashboard, logging system and API.

Regular Dedicated Maintenance - AMERICASScheduled for Nov 17, 2026 · 5h 0mScheduled

We are conducting regular maintenance on our systems. This can lead to short interruptions for connections with the dashboard, logging system and API.

amazee.io Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a amazee.io 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 amazee.io Outage Reports

Problems reported by engineers using amazee.io. 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 amazee.io problems reported yet.

Something wrong with amazee.io on your end?

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

About amazee.io

amazee.io's status page at status.amazee.io lists 29 components, such as amazee.ai infrastructure: au103, au2.lagoon and ca1.lagoon. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on amazee.io's side or yours.

amazee.io Status FAQ

Is amazee.io down right now?

The verdict at the top of this page comes from the latest poll of the official amazee.io 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 amazee.io 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 amazee.io recovers.

How do I check amazee.io uptime history?

PulsAPI tracks amazee.io 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 amazee.io changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect amazee.io outages?

PulsAPI reads the official amazee.io 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 amazee.io components?

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

Can I get alerts when amazee.io goes down?

Yes. Create a free account and subscribe to amazee.io: 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 amazee.io 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 amazee.io problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor amazee.io?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so amazee.io 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 amazee.io 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