I can upload models, I can see the camera feed (Prusa Buddy3D Camera), and most of the time (unfortunately not always) I receive notifications on the iOS PRUSA app. But the displayed printer status is OFFLINE. This is true in an external browser, in Prusa Connect within PrusaSlicer (MacOS and Linux tested), and in the iOS app. Very rarely does it show the status as ONLINE for a few minutes, but it’s always only in one of the mentioned places — never in all of them (web, slicer and iOS) at the same time.

And in the last few days, I’ve started getting iOS notifications saying “printer requires attention.” But when I go to the printer, everything is perfectly fine—the printer is printing, and there’s no problem shown on the display either.

PS: I've posted the same report on GitHub https://github.com/prusa3d/PrusaSlicer/issues/13935#issuecomment-4243255633 as it was the best "issue" I was able to find

So this time I did not bother to contact support, and rather deleted / reinstalled - annoying,  in particular as the print history in Connect is lost, but takes only a couple of minutes vs hanging around with support for hours and coming to the same result. 

Klaus

lost a 12 hour print at 87% due to “g-code transfer too slow”

my internet is fine. The buddy3D camera still shows.

Prusa connect status shows “error: bug”

very cool. I was considering picking up a second core one as I have a bunch of spare parts, but I’m thinking of just selling it at this point. I am tired of these errors not being prioritised by Prusa.

Posted by: @kgapp

Seems that is still unresolved. Today again the Printer Offline thing.

Strange enough, the App on the Mobile phone shows "Online" and notifies me about a finished print....

Klaus

Strange enough, the App on the Mobile phone shows "Online" and notifies me about a finished print....

Klaus

Posted by: @same-old-shane

Just to give an update of the last issue with Prusa connect, 

Service Update: Resolution of Connection Issues
Summary Last night, our services experienced a temporary disruption. We are pleased to confirm that all systems are now fully operational.
What Happened The incident began with an unexpected database issue that caused a brief service interruption. As systems began to recover, a surge in automated reconnection attempts from customer devices created a high-volume traffic spike. This "retry storm" mimicked the patterns of a DDoS attack, leading to extended periods of high latency and connection failures.
Our Response * Rapid Detection: Our supervising team was alerted by user reports and internal monitoring, triggering an immediate emergency response.

• Mitigation: We implemented traffic shedding and resource scaling to stabilize the environment and process the backlog of requests.
• Next Steps: Our specialists are conducting a full Root Cause Analysis (RCA) to identify the database trigger and implement new rate-limiting precautions to prevent similar "retry storms" in the future.

We appreciate your patience while our team worked through the night to restore your service.

• Mitigation: We implemented traffic shedding and resource scaling to stabilize the environment and process the backlog of requests.
• Next Steps: Our specialists are conducting a full Root Cause Analysis (RCA) to identify the database trigger and implement new rate-limiting precautions to prevent similar "retry storms" in the future.

Posted by: @same-old-shane

Hiya, 
Already reported and is being looked into. Checking to see if monkeys got into the wrenches, or if the hamsters need to be fed. 
But reports filed, awaiting for resolve.