Why http://rendezvous.appinventor.mit.edu/ is down?

Check by restarting your browser.

Don't you think I already tried it?

I don't think so!

It works fine for me too but on mobile data it doesn't works on wifi. seems like isp is doing something fishy.

1 Like

Then you have to contact your ISP about that, until then, connect your mobile network with USB cable.

1 Like

Actually my isp has blocked this ip:

Wait why did you leak your IP address?

It isn't mine, this is the ip of http://rendezvous.appinventor.mit.edu/ server.

So, your ISP unblocked it?

It's very simple thing that my isp has blocked this ip and I never said that they unblocked it.

you didn't understand my sentence. i said they unblocked it now?

I agree, working fine for me also.

1 Like

As nice as this URL is for capacity planning, I wonder if there a URL I could query for a more fine grained history, like hourly totals.

I ask because I have seen reports of Companion disconnection, and experienced it myself.

I don't know yet if it might be caused by any of

  • battery saver kicking in on my device
  • peak capacity surge at MIT
  • behind the scenes server juggling at MIT
  • competition for hash codes for rendezvous requests

If any one has a good link for this, I would like to add it to


The Rendezvous server is only involved in connection initiation. Once the Companion and your browser are in contact, it has no continuing role. So if you get disconnected once connected, the problem is not the Rendezvous server.

What is the name of the ISP that is blocking the Rendezvous server? I may be able to contact them to find out why they put the block in place. I suspect that they saw some number of their customers connecting to it (meaning they are using App Inventor) and assumed it is a malware command and control server!



Thank you for the response.

In light of that, and because the majority of my Companion disconnections happen to my phone, and rarely to emulated Companions, I am leaning towards blaming my phone' s battery saver settings for Companion disconnections.


I'm curious. Do the disconnections happen with a legacy connection or the non-legacy (WebRTC) connection or both?

1 Like

This is an Android 8.1 system notification using WebRTC I just started receiving.

1 Like

I just tested using a default WebRTC connection, and let my phone's battery saver lock it.
No disconnection.

I haven't used a legacy connection for weeks.

I'm on the Eastern US seaboard so things are quiet here.

I lack enough data to see a pattern yet.

1 Like

It happens randomly and on both connections. Btw my isp now unblocked this and now my companion works fine.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.