Current logo

Is Current Down?

DatabaseLive status, outages, and incident history

No. Current is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment Current breaks

Current 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 Current status page
How we know: the official Current status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Current Status Summary

As of 13:21 UTC on 9 November 2026, Current is operational. PulsAPI checked Current's official status page and found 6 of 6 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Current, counting degraded performance as up. The latest incident, "[Azure ServiceHealth] Network Infrastructure - West Europe", was on Oct 28, 2026 and lasted 1h 27m.

Cite as: PulsAPI, “Current status”, checked 9 November 2026, 13:21 UTC. https://www.pulsapi.com/services/current

Current Component Status

The main Current systems on this page. All 6 are operational right now.

6operational
Console & API
Operational
Data Movement & Connectors
Operational
Data Protection & Recovery
Operational

3 more components tracked

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

Also tracking Database - Control Plane Actions, Database - Data Plane and Core Availability, Observability.

See all of them free

Component statuses may change independently during partial outages.

Recent Current Outages & Incidents

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

[Azure ServiceHealth] Network Infrastructure - West EuropeResolved Oct 28, 2026 · 1h 27mResolved

**Degraded connectivity in Azure West Europe** Since 17:36 UTC, customers may experience increased latency or intermittent connection issues when accessing databases hosted in Azure West Europe. Azure has identified a network infrastructure issue and is actively working to mitigate it. We are monitoring the situation and will provide updates as more information becomes available.

Tiger Cloud Databases running on Azure West Europe RegionResolved Oct 9, 2026 · 1h 31mResolved

Starting at approximately 12:30 UTC, some Tiger Cloud database services running in our Azure West Europe region became unavailable. The disruption was caused by an incident on the Microsoft Azure platform (Azure Tracking ID: NZ_2-W58), which rendered certain virtual machines unreachable and prevented storage disks from attaching. Services in other regions and cloud providers were not affected. Current Status: RESOLVED As of 15:44 UTC, all affected database services in the Azure West Europe region have been restored and are running normally. We are continuing to monitor the region until Microsoft Azure officially closes their incident. If you are still experiencing issues with a service in Azure West Europe, please contact our support team with your project and service IDs.

Azure VM stability issues in Germany West CentralResolved Oct 8, 2026 · 28 minResolved

Customers may experience service availability issues in Germany West Central due to ongoing problems affecting Azure in the region. We are monitoring the situation and will provide updates as more information becomes available.

Current Uptime History

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

Uptime history91 days observed
Aug 1199.23% average · 6 days with incidentsNov 9

Going further back: Current uptime by month and every recorded Current outage.

Live Current Outage Reports

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

Something wrong with Current on your end?

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

About Current

Current publishes overall service health on its public status page at status.tigerdata.com. PulsAPI tracks Current outages, degraded performance and incident history in real time, alongside the rest of your database stack.

Over the past 30 days, PulsAPI has measured Current uptime at 100.00%. Response times, incident history, and SLA tracking for Current are available on the PulsAPI dashboard.

Current Status FAQ

Is Current down right now?

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

How do I check Current uptime history?

PulsAPI tracks Current uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Current changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Current outages?

PulsAPI reads the official Current 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 Current components?

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

Can I get alerts when Current goes down?

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

Is there a free way to monitor Current?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Current 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 Current with the rest of your stack

2660+ 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