Is Central 1 down?

Last checked 6m ago
Current status
Central 1 is up

No incidents right now.

Official status page: https://status.central1.com · Polled every 5 minutes · 5 components tracked

Real-time Central 1 status, recent outages, and incident history — pulled directly from Central 1's official status page at https://status.central1.com every 5 minutes. Pingoru tracks 5 Central 1 services and has captured 37 incidents in the last 90 days (95.88% uptime). Get email, Slack, Discord, or webhook alerts the moment Central 1 reports a new incident — free for 5 monitors, no credit card.

Users who monitor Central 1 also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
Central 1 uptime 95.88% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Resolved 4h 16m
    Started Apr 27, 2026, 02:38 PM UTC · Resolved Apr 27, 2026, 06:54 PM UTC
    Payment Services
    2 updates · show timeline
    • identified · Apr 27, 2026, 02:38 PM UTC

      Payments Canada has notified Central 1 that BNC (National Bank of Canada) did not send one of the two files in the morning exchange. The larger of the two AFT files was successfully received and processed. We will provide an update once we have received and processed the remaining BNC file. Central 1 – [email protected] – 1.888.889.7878, press 1

    • resolved · Apr 27, 2026, 06:54 PM UTC

      We have received this mornings missing AFT file from BNC. The 160 transactions missed in the file this morning will be included in this afternoon's AFT CR03/ON03. Central 1 – [email protected] – 1.888.889.7878, press 1

    Latest: We have received this mornings missing AFT file from BNC. The 160 transactions missed in the file this morning will be included in this afternoon's AFT CR03/ON03. Central 1 – Suppo…

  2. Resolved
    Started Apr 25, 2026, 06:28 PM UTC · Resolved Apr 25, 2026, 06:28 PM UTC
    Payment ServicesDigital Banking Services
    1 update · show timeline
    • resolved · Apr 25, 2026, 06:28 PM UTC

      Central 1 is aware that users were not seeing the OAS production login link on the Client Centre. The link for OAS has been restored. Central 1 - [email protected] - 1.888.889.7878, press 1

    Latest: Central 1 is aware that users were not seeing the OAS production login link on the Client Centre. The link for OAS has been restored. Central 1 - [email protected] - 1.888.889.7…

  3. Resolved 14h 27m
    Started Apr 22, 2026, 08:56 PM UTC · Resolved Apr 23, 2026, 11:23 AM UTC
    Payment ServicesTreasury ServicesIncident Alerting
    5 updates · show timeline
    • investigating · Apr 22, 2026, 08:56 PM UTC

      We are currently investigating an issue impacting Wires. At approximately 1:25 p.m. PT (4:25 p.m. ET), we observed incoming and outgoing wires not moving in our system. At this time, we are working to validate scope. We will provide an update within 30 minutes or sooner as more information becomes available. Central 1 – [email protected] - 1.888.889.7878, press 1

    • investigating · Apr 22, 2026, 09:22 PM UTC

      Fiserv has raised a critical incident and have their team engaged reviewing a core issue within their infrastructure causing impacts to our wires system. As a workaround, Central 1 is currently manually releasing incoming and outgoing wires. The work around will prevent any further delays in wires processing while Fiserv continue to triage their incident. We will provide an update within 1 hour or sooner as more information becomes available. Central 1 – [email protected] - 1.888.889.7878, press 1

    • monitoring · Apr 22, 2026, 10:26 PM UTC

      Central 1 has been able to manually process incoming and outgoing wires up to 3 p.m. PT (6 p.m. ET) wires close time (SWIFT gateway closed). Fiserv continues to triage their critical incident and have Central 1 teams engaged to ensure we can establish connectivity with their system. Central 1 and Fiserv will work to ensure there is system stability for tomorrow mornings 5 a.m. PT (8 a.m. ET) wires opening. We will provide an update tomorrow at 5:30 a.m. PT (8:30 a.m. ET). Central 1 – [email protected] - 1.888.889.7878, press 1

    • monitoring · Apr 23, 2026, 03:08 AM UTC

      Fiserv has provided an update to Central 1 that they have resolved their technical issues within their Azure environment. Central 1 and Fiserv will complete additional validation steps to ensure system stability prior to Wires business hours resuming tomorrow morning at 5 a.m. PT (8 a.m. ET) wires opening prior to confirming the incident is resolved. We will provide another update tomorrow by 5:30 a.m. PT (8:30 a.m. ET).

    • resolved · Apr 23, 2026, 11:23 AM UTC

      Central 1 has confirmed that both outgoing and incoming wire transfers have resumed normal processing. Central 1 – [email protected] - 1.888.889.7878, press 1

    Latest: Central 1 has confirmed that both outgoing and incoming wire transfers have resumed normal processing. Central 1 – [email protected] - 1.888.889.7878, press 1

  4. Resolved 12d 17h
    Started Apr 16, 2026, 07:28 PM UTC · Resolved Apr 29, 2026, 01:26 PM UTC
    Digital Banking Services
    7 updates · show timeline
    • investigating · Apr 16, 2026, 07:28 PM UTC

      Please be advise that International transfer services are currently unavailable in online banking. We are conducting a thorough analysis of the systems involved and working towards resolving the issue. We will provide an update on or before Friday April 17, 2 p.m. PT / 5 p.m. ET. [email protected] - 1.888.889.7878, option 2

    • investigating · Apr 17, 2026, 09:24 PM UTC

      We are continuing to investigate the root cause of the international transfer service interruption. Our technical teams remain focused on the analysis and resolution process. We will provide the next update on or before Monday, April 20, by 2 p.m. PT / 5 p.m. ET.

    • investigating · Apr 21, 2026, 06:17 PM UTC

      We are continuing to investigate the root cause of the international transfer service interruption. Our technical teams remain focused on the analysis and resolution process. We will provide the next update on or before Tuesday, April 21, by 2 p.m. PT / 5 p.m. ET.

    • investigating · Apr 24, 2026, 12:33 AM UTC

      We believe we have identified the root cause of the International Transfer Service interruption. A fix has been applied in our lower environments and is currently undergoing testing. Our technical teams are closely monitoring results as we progress toward resolution. We will provide the next update on or before Monday, April 27, by 2 p.m. PT / 5 p.m. ET [email protected] - 1.888.889.7878, option 2

    • investigating · Apr 27, 2026, 10:43 PM UTC

      Our teams continue to validate the fix identified for the international transfer service interruption. We are tentatively targeting a resolution later this week, pending successful testing. We will provide the next update tomorrow, on or before 2 p.m. PT / 5 p.m. ET. [email protected] - 1.888.889.7878, option 2

    • investigating · Apr 28, 2026, 08:45 PM UTC

      Please be advised that a fix will be deployed with Urgent Digital Banking Core Release 768 (CHG170247) The release has been scheduled for Wednesday April 29, 2026 at 1 a.m. PT (4 a.m. ET). [email protected] - 1.888.889.7878

    • resolved · Apr 29, 2026, 01:26 PM UTC

      Please be advised that the urgent release is deployed and International Transfer is available in online banking.

    Latest: Please be advised that the urgent release is deployed and International Transfer is available in online banking.

See the full Central 1 outage history

27 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 16 incidents
  • INC220625 - BNC missed sending an AFT file in the morning exchange Resolved
    Started Apr 27, 2026, 02:38 PM UTC · Resolved Apr 27, 2026, 06:54 PM UTC · 4h 16m
  • Resolved - INC220570 - OAS link not available Resolved
    Started Apr 25, 2026, 06:28 PM UTC · Resolved Apr 25, 2026, 06:28 PM UTC ·
  • Resolved - INC220447 - Issue Impacting Wires Resolved
    Started Apr 22, 2026, 08:56 PM UTC · Resolved Apr 23, 2026, 11:23 AM UTC · 14h 27m
  • Resolved - INC220338 – Central 1 UCS 43-minute Service Degradation Resolved
    Started Apr 20, 2026, 11:45 PM UTC · Resolved Apr 20, 2026, 11:45 PM UTC ·
  • INC220280 - Incoming/outgoing wires not processing Resolved
    Started Apr 20, 2026, 12:15 PM UTC · Resolved Apr 20, 2026, 02:49 PM UTC · 2h 33m
  • INC220280 - Incoming/outgoing wires not processing Resolved
    Started Apr 20, 2026, 12:14 PM UTC · Resolved Apr 20, 2026, 12:11 PM UTC ·
  • INC220235 - RESOLVED - PaymentStream Direct not accessible Resolved
    Started Apr 19, 2026, 07:04 PM UTC · Resolved Apr 19, 2026, 07:47 PM UTC · 42m
  • INC220098 : International Transfer Service Interruption Resolved
    Started Apr 16, 2026, 07:28 PM UTC · Resolved Apr 29, 2026, 01:26 PM UTC · 12d 17h

See Central 1 in your Pingoru dashboard

Monitor Central 1 alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Central 1 to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Central 1 incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Central 1 or see every provider at once.

Maintenance calendar

Scheduled Central 1 maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Central 1 status change, one inbox

Pingoru watches Central 1's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Central 1 reports on 5 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Central 1 alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Central 1 maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Central 1 services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Central 1 from the same account, with per-user notification preferences for any monitor.

Get notified on Central 1 status changes

Pingoru watches Central 1's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Central 1 free

Monitor Central 1 along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Central 1 and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Central 1 uptime & incident history

See 90 days of Central 1 uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Central 1 uptime history

Frequently asked questions

What is Central 1's uptime?
Over the last 90 days, Central 1 reported 95.88% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.central1.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Central 1's uptime history rolling forward in real time.
Has Central 1 had outages in 2026?
Yes — Central 1 has had 37 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Central 1 outage?
The most recent Central 1 incident was "CHG170247 - Urgent Digital Banking Core Release 768", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.central1.com. See the full incident card above for affected components and the update timeline.
How often does Central 1 have outages?
Based on the last 90 days, Central 1 averages 12.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Central 1's status page?
Central 1's official status page is https://status.central1.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Central 1 down right now?
Central 1 is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Central 1 reports a change. Current status is based on 5 tracked services.
How does Pingoru know if Central 1 is down?
We read https://status.central1.com directly, using Central 1's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Central 1 has an outage?
Create a free Pingoru account and add Central 1 as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Central 1's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Central 1 incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Central 1 issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Central 1 status?
We use Central 1's own status page at https://status.central1.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Central 1 components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Central 1's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Central 1 free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →