Apple auth issues
Signing in with Apple is slow or fails for some users. This affects sign-in to Lovable and to apps built with Lovable. Lovable reports that the team is investigating.
State
Investigating
Started
Ongoing for
28 min
Worst impact
Degraded
Timeline
1 updateInvestigating
28 min 100%
Updates
Times in UTCAs posted by Lovable
Signing in with Apple is currently slow or failing for some users. This affects signing in to Lovable and signing in to apps built with Lovable. Our team is investigating.
Lovable in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
24
Median duration
58 min
This incident
51% shorter than the median
Other Lovable incidents
All incidentsLovable·Some users may see errors or delays when the Lovable agent works
Some users saw errors or delays when the Lovable agent worked on their projects. Lovable reports that the incident is resolved. It lasted 17 minutes.
Lovable·Database creation failures in APAC
Lovable reports that database creation for projects in the Asia-Pacific region did not work. Some users in Tokyo could not create databases. Lovable reports that the database provider recovered and the incident is resolved. The outage lasted about 2 hours.
Lovable·Degraded Lovable Cloud project creation
Lovable Cloud project creation did not work for some users. The vendor reported degraded performance in its US-West-2 region. Lovable reports that this incident is resolved. It lasted 81 minutes.
Lovable·Project previews failing to load or loading slowly for some users
Lovable reported that project previews failed to load or loaded slowly for some users, mainly in the New York and New Jersey area. Lovable monitored the fix and then reported the incident resolved. The outage lasted 95 minutes.
Lovable·Some Lovable Cloud apps unable to reach backend
This incident has been resolved.
Follow Lovable
Your coding agent knows when Lovable is down, and tells you when a failure is theirs, not yours. You can also get Lovable incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "lovable" and tell me if Lovable has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=lovable/feed subscribe https://outages.live/feed.xml?providers=lovableFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane