Resolved on December 15, 2025.
At approximately 10:45 AM PST, our team identified a service disruption affecting the EAM product, which caused all users to potentially see a "Failed to fetch" error message. Our engineering team immediately began investigating and was able to quickly identify the root cause of the issue. A fix was promptly implemented and deployed, and we have confirmed stability across the platform. Most users should now be able to access the EAM product as usual. If you continue to experience any difficulties, please perform a hard refresh of your browser or application. We appreciate your patience and apologize for any inconvenience this brief disruption may have caused.
Update timeline
- resolved Dec 15, 2025, 07:19 PM UTC
At approximately 10:45 AM PST, our team identified a service disruption affecting the EAM product, which caused all users to potentially see a "Failed to fetch" error message. Our engineering team immediately began investigating and was able to quickly identify the root cause of the issue. A fix was promptly implemented and deployed, and we have confirmed stability across the platform. Most users should now be able to access the EAM product as usual. If you continue to experience any difficulties, please perform a hard refresh of your browser or application. We appreciate your patience and apologize for any inconvenience this brief disruption may have caused.
Your product runs on more than Spare
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services