Same here
Hello MIT App Inventor Team,
We are currently encountering a 504 Gateway Time-out (nginx) error while accessing the MIT App Inventor login page:
The page consistently fails to load and shows a 504 error, preventing teachers and students from logging in. This is directly impacting ongoing live classes.
The issue has been observed across multiple browsers and networks, so it appears to be server-side.
Could you please confirm if there is an ongoing outage and share an estimated timeline for resolution?
Screenshot attached for reference.
Thank you for your support. Looking forward to your update.
CC: @ewpatton
Best regards,
Freeda Felix K
Curriculum Team
Codingal Inc.
I have assigned one of the App Inventor developers. Remember the time difference in Boston. It is 6 in the morning there, so please be patient.
pls be quick i am getting the same error at my end
I have the same problem with the Gateway timeout(
Moreover, blocks Drag-n-Drop function doesn't work on the Offline version.
What's the problem?
Don't know, just be patient. Like I said it is now 6:30 in the morning in Boston. They have terrible weather also.
App Inventor has no offline version
I hope everyone is save.
We are facing gateway timeout issue when we try to open the MIT App inventor. Kindly advice.
It seems the server of MIT app inventor is totally down and it is giving a gateway timeout error when you try to the MIT app inventor. Kindly advice
This might be the cause:
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 27, 2026 - 06:30 EST
Scheduled - Due to scheduled network maintenance, MITnet BMS network — will be intermittently unavailable in Building 11 on Tuesday 1/27/26, between 6:30am and 9:00am
Brief isolated outages will occur throughout the window as upgrades are performed on each switch.
If you experience any network issues after the maintenance period, please contact the Service Desk at 617-253-1101 or servicedesk@mit.edu.
Jan 27, 2026 06:30-09:00 EST
noo i can't do my hw and the due date is 11pm
It seems to be solved for me.
back up on code server here too
The cluster where most of our services reside, including the login server, lost the majority of its machines. We've brought them back online but are still trying to identify a potential root cause.