bmercier

Most likely, this is what is happening;
1. You have eisy-ui installed. When installed, eisy-ui service is responsible for the portal connectity.
2. You started AC, and connected using port 8443 or 8080 (Directly to IoX). In that case, IoX no longer has the portal connectivity, It can't give you a portal status, and you can't approve/revoke portal access from an account. The error is expected.
When eisy-ui is installed, it's best to connect to port 443 or 80 (same url, just a different port). Then, the portal tab will work as expected. Note that when eisy-ui is installed, you can also use the Web UI to access the same functionnality. 

Here's a few tips regarding Alexa.
When troubleshooting, always use the Alexa app, instead of voice commands. This way, you are sure about what device is being controlled. When controlling via voice, Alexa may be confused with a device or room using a similar name.
If you find you have duplicates, you need to delete them from the Alexa app. You may be tempted to start fresh and delete your mappings on portal, but there is no need to do that. The only case where it may be useful is if you are mapping an ISY node that no longer exists on your ISY (or eisy/polisy). 
When using V3, when adding/editing/removing a mapping, it should be updated directly in the Alexa app. There is no need for a device discovery. That's if the skill is linked. If you change your mapping while the skill is not linked, then when linking it will get discovered.
I don't think the problem you are having is the alternate spoken. Alternate spokens are treated exactly the same way as the primary name you gave. Using alternate spoken just creates additional Alexa devices mapped to the same ISY node.
One thing to watch for are Alexa scenes, especially if you had some when using V2. Alexa scenes are kind of hidden. So if you have an Alexa devices with the same or similar name as an Alexa scene, then Alexa will see multiple device with the same name. That's why it's important to first test controlling devices directly with the Alexa app - you know which one you are controlling.

This skill is definitely outdated.
Please use "ISY Optimized for Smart Home V3".

Ring advised me of another upcoming change. I had to make another release of the plugin, version 1.2.6. Please update when you have a chance.
For now, 1.2.5 works. However the authentication should start to fail in the next few days if you don't update.

Everything should be up now.

This error message means that it is receiving too many requests from a user interface - either UD Mobile or a web browser. This is tripping the rate limiter.
Check the browser log for unusual activity. Check the PG3 log as well.
Something might be stuck in a loop somehow.
A reboot might be required.

You can see the releases notes in the plugin store. Click on Ring, then More info.
Or here: https://github.com/UniversalDevicesInc/ring/blob/master/README.md

I investigated this and found the source of the problem.
I made an update to Portal. Will be live soon.

Can't do that.
If you revoke, you can't re-approve it. You will have to remove the uuid from your account and re-add it... which will also remove your Alexa/Google/IFTTT config.

So here's what happened.
There were 2 bugs in the code of the proxy servers that were dormant. They had no effects, unless a proxy server had a hard stop... which happened last night. 
The first bug had the effect that some units were trying to connect to a no longer existing proxy server.
The second bug is more complicated to explain, but it was also caused by the hard stop. This one was causing the HTTP 500.
The hard stop was caused by AWS stopping one of our proxy instance unexpectedly. This was NOT a graceful shutdown. This is usually caused by the failure of the underlying hardware.
Both bugs have been fixed and are in production.

Problem has been resolved.
It may take a few minutes for all units to reconnect to portal.

This means that your eisy is indeed not connected to portal. For your undertanding, the connectivity from eisy to portal is initiated by eisy. 
If everything else works on eisy, then it could be a bad internet switch or port, patch cord, or perhaps the router not allowing internet access to eisy.

Contact & motion sensor events are debounced. There can't be more than 1 event within a 30 seconds period. So this is likely the reason if you are testing 2 doorbell rings within 30 seconds.
This is implemented within our Alexa skill.

I would suggest to try a different browser, or perhaps try incognito mode (If using Chrome).
I believe a browser extension is probably interfering somehow.
You could also try to press F12 and look at the browser console, then navigate to my.isy.io. You may see in the console an error message that could give you a clue.

Thanks for reporting this.
Please try again. I just forgot to push a commit.

First, please go to the Plugin store and click on "Refresh Store".
Then, you can try to restart the plugin. If it has been reinstalled in an attempt to fix it, it should be reinstalled again as the installed edition will be "Free", instead of "Standard" as it should.

Version 1.2 has no functional changes.
The main difference is that it is now using the UDI python interface's OAuth class.
If after updating there are oAuth errors, then a re-authorize should fix it.

Should be fixed now.

Have you tried to update your firmware?
In the admin console, click on upgrade packages.

It is indeed down:
https://status.ring.com/

Alexa routines should work well now for everyone.

Please wait a few more minutes. Although the maintenance is completed, not all units have reconnected to the portal. 
We currently have about 75% of the units reconnected.
I should have added that information in the notice.

My apologies, there was a bug, and it is now fixed. You should be able to by a license now.
You don't have to wait to the end of the trial. If you buy now, it will be added to the end of the existing license.

Should be working for everyone now.

This is now fixed. 
This is definitely a popup that had no functional impacts.