Griffin logo

Is Griffin Down?

FinTech & PaymentsLive status, outages, and incident history

No. Griffin is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment Griffin breaks

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

Status report

Griffin Status Summary

As of 19:39 UTC on 14 November 2026, Griffin is operational. PulsAPI checked Griffin's official status page and found 7 of 7 components operational, with no active incidents. The latest incident, "Delayed FPS payments", was on Oct 16, 2026 and lasted 1h 45m.

Cite as: PulsAPI, “Griffin status”, checked 14 November 2026, 19:39 UTC. https://www.pulsapi.com/services/griffin

Griffin Component Status

The main Griffin systems on this page. All 7 are operational right now.

7operational
API
Operational
App
Operational
Customer support
Operational

4 more components tracked

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

Also tracking Inbound payments, Outbound payments, Sandbox, Verify.

See all of them free

Component statuses may change independently during partial outages.

Recent Griffin Outages & Incidents

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

Delayed FPS paymentsResolved Oct 16, 2026 · 1h 45mResolved

We are back up and running! We are pleased to report that **[the issue]** has been resolved. Our app is now operating normally. Thank you for your patience and support during this time. If you experience any further issues, please do not hesitate to reach out to our support team at [support@griffin.com](mailto:support@griffin.com). --- [2026-10-16T11:42:26Z] (identified) We have raised the issue with our banking partner and are working with them to resolve it. Some Faster Payments are still being delayed. Affected payments have not been lost and will be processed as soon as the delay is resolved. No action is needed from you. --- [2026-10-16T11:03:12Z] (investigating) We are currently experiencing a delay in Faster Payments (FPS). Our team is investigating this as a high priority. We apologise for any inconvenience this may cause and thank you for your patience. Stay tuned for updates.

Settings page components - unavailableResolved Aug 28, 2026 · 1h 18mResolved

We are pleased to report that the issue has been resolved. Our app is now operating normally. If the Settings page still isn't working for you, please refresh the page bypassing the cache: `Cmd+Shift+R` on Mac (`Cmd+Option+R` in Safari), or `Ctrl+Shift+R` on Windows/Linux. Thank you for your patience and support during this time. If you experience any further issues, please do not hesitate to reach out to our support team at [support@griffin.com](mailto:support@griffin.com). --- [2026-08-28T12:55:08Z] (monitoring) We are actively working on a fix. Our engineers have developed a solution, which is being tested internally. We are monitoring the system at the moment and will provide an update within 1 hour. Please bear with us as we work to restore normal service. Your patience is greatly appreciated. --- [2026-08-28T12:31:12Z] (investigating) We are currently experiencing issues with our settings page within our app. All settings besides webhooks are currently unavailable. Our team is investigating this as a high priority, and we're working to resolve the issue as quickly as possible. We apologise for any inconvenience this may cause and thank you for your patience. We will provide an update on progress made in 1 hour. Stay tuned for updates.

Griffin Uptime History

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

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

Something wrong with Griffin on your end?

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

About Griffin

Griffin's status page at status.griffin.com lists 7 components, such as API, App and Customer support. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Griffin's side or yours.

Griffin Status FAQ

Is Griffin down right now?

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

How do I check Griffin uptime history?

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

How fast does PulsAPI detect Griffin outages?

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

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

Can I get alerts when Griffin goes down?

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

Is there a free way to monitor Griffin?

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