No reported issues with this provider’s services in the last 24 hours.
Epos Now status history
Down
Warning
Jul 26
Aug 2
Aug 9
Aug 16
Aug 23
Aug 25
Aug 30
Sep 1
Sep 6
Sep 8
Sep 13
Sep 15
Sep 20
Sep 22
Sep 24
Sep 27
Sep 29
Oct 1
Oct 4
Oct 6
Oct 8
Oct 11
Oct 13
Oct 15
Oct 18
Oct 20
Oct 22
Incidents
Provider incidents
Degraded21 Oct at 14:03 UTC
Resolved
Cloud sync intermittent issue
A fix has been found and released to Production. Only affects a very select few customers; please sync the cloud to receive the latest update within the next 30 minutes.
The issue has been identified and a fix is being implemented.
We are continuing to investigate a further fix. We have released an update to fix this, which will help a few extra affected customers. Please cloud sync to get the latest update; the update will come out next at 17:30 BST
This incident has been resolved. Please cloud sync, thank you for your patience.
Degraded21 Oct at 07:36 UTC
Resolved
Cloud Sync Intermittent Availability
We are investigating an intermittent availability of Cloud Sync Services. Our team is investigating and will update in due course.
Our team continues to investigate the issue with Cloud Sync services impacting some customers, your till will continue to store transactions locally.
We’ve identified the cause of this issue. A specific hardware configuration used by some customers is preventing their tills from connecting to our servers. Our team is working on a fix now. Your till will continue to take payments and store transactions locally, and these will sync once the issue is resolved. We’ll post another update by 10:30 BST.
We’ve identified the cause as a security certificate issue that stops some till hardware connecting to our servers. Most customers are unaffected. We’re testing a fix in a separate environment first. Your till will keep storing transactions locally, and these will sync once the fix is live. Next update by 12:00 BST.
We’ve identified the cause as a security certificate issue that stops some till hardware from connecting to our servers. Most customers are unaffected. We’re testing a fix in a separate environment first. Your till will keep storing transactions locally, and these will sync once the fix is live. Next update by 14:00 BST unless fixed before.
A fix has been found and released to production. We will continue to monitor for any more issues. Thank you for your patience.
The fix has been deployed and the issue is now resolved.
Outage20 Oct at 11:10 UTC
Resolved
Cloud Services
We are currently experiencing a wide spread Cloud Services outage due to a 3rd party infrastructure provider. Our team is working to resolve, we advise customers to revert offline processing and offline mode.
Our team is working on implementing the resolution to mitigate the impact and expect to see recovery within 20 minutes.
Our team continues to work on resolving the issue, we will provide an update as soon as possible.
The issue is now resolved and services should be back operational. Our team will continue to monitor closely, we recommend refreshing pages / applications if you are still experiencing the issue.
This incident has been resolved.
Degraded20 Oct at 10:55 UTC
Resolved
Cloud Services
We are currently investigating an issue with Cloud Services across all Epos Now services.
Degraded3 Oct at 21:06 UTC
Resolved
Epos Now Login Service - Unavailable
We are investigating an incident where users are unable to log in to Epos Now services, our team is currently investigating and will provide updates as they become available.
We have identified the issue and our team is working on resolving, customers already logged in to Epos Now services are unaffected.
A fix has been deployed and all services should be restored, our team will monitor performance to ensure no further impact.
The incident has now been resolved.
Saw an error in description or reports for Epos Now?
Frequently asked questions
Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.
Is Epos Now down right now?
No. Epos Now currently reports normal operation on its official status page. PayAtlas last checked it today at 01:13 UTC.
What do Operational, Degraded, Outage and Resolved mean?
They are the states Epos Now publishes on its official status page. Operational means the service works normally. Degraded means part of it is slower or failing for some customers, regions or payment methods, while the rest still works. Outage means a major disruption: a service, or a key part of it, is unavailable. Resolved marks an incident Epos Now has closed; the time it was resolved shows when you hover it.
Does this confirm that my merchant account or customers are affected?
Not on its own. Firemap shows what Epos Now publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Epos Now support with specific transaction IDs if you see failures.
Where does Firemap get this status information?
From official status pages only. Firemap reads each page it tracks automatically every few minutes and records every status change and incident the provider publishes there. Nothing about Epos Now is added or edited by hand.
Why can official and community signals disagree?
They come from different sources. The official status is what Epos Now has confirmed, and providers often post an incident only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.
What should I check before changing payment routing?
Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.
What is Firemap’s coverage and method?
Firemap tracks the official status pages of payment providers listed on PayAtlas. Each page is checked automatically, and every incident is stored with its start time and, once resolved, its end time. When Firemap has data for Epos Now, this page shows up to 90 days of status history and incidents from the last 30 days.
What can Firemap confirm, and what can’t it?
Firemap can confirm only what Epos Now has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Epos Now says so, and it cannot see problems the provider has not reported.
Save the providers you work with and get instant access to their status, coverage, insights,
comparisons, and recommended alternatives whenever you need them.
Cookies enable us to store your preferences and give you a personalized website experience.
We also use cookies for analytics and targeted marketing.
We respect your right to privacy, so you can choose not to allow some types of cookies.
Read our Cookies Policy to learn more.
Necessary Required
These cookies are crucial for the website to perform its main functions and associated services. Simply put: the site can't fully function without them, so disabling them isn't an option.
Marketing
To bring you the most relevant content, we and our advertising partners use marketing cookies. If you choose to disable them, you might see less relevant ads.
Analytics
Analytics cookies provide anonymous insights into how visitors engage with the PayAtlas website, helping us improve user experience and functionality.
Deny
Save My Preferences
PayAtlas
Share your feedback
It goes to our team and shows up on the public board.