Pokemon Go Regidrago Raid Error 36, Players Cannot Join Elite Raids
Update: Niantic and Pokemon Go will be hosting another Elite Raid Day on March 12, 2023.
We have resolved an issue preventing Trainers from joining Elite Raids. By way of apology, we have added an additional day of Elite Raids on March 12 local time for Trainers in the GMT +13 timezone. Thanks for your understanding.
— Niantic Support (@NianticHelp) March 10, 2023
Update: Trainers, it seems like they fixed the “Cannot Join Raid Group Error 36,” but there is another issue now – Regidrago’s catch circle is bugged.
Previous Story: Trainers, Regidrago Raid Eggs have hatched, but unfortunately, players are unable to join Regidrago Raids due to an error.
“Cannot Join Raid Group Error 36” is the message that Pokemon Go players are getting when trying to do Regidrago Raid. Elite Raid Eggs have hatched but players are unable to join the raid lobby. Lobbies are all at zero, and we players are not happy about it.
Niantic and Pokemon Go should take a look at this issue as soon as possible. There is no info on how to fix this issue at the moment, so if something comes up, we will let you know.
“Today we want to share our renewed commitment to bolstering Pokémon GO’s in-person experience. We have a lot planned for 2023, but first, we’d like to recap some of our recent updates and share additional updates that are coming soon,” is what they announced prior to launching the Regidrago Elite Raids.
Do you have any issues when trying to join Regidrago Raid? Let us know in the comments below.
Cannot joint elite raids in New Zealand. Local Raid box is green but get error 36
11 am raid mine wasn’t caught or ran just gone / even journal showed items from raid but no catch or ran away after after midday egg disappeared no 2 pm raid or 5 by look of it
Toujours impossible de rejoindre le raid aujourd’hui, 12 mars.
Erreur 36
As of July 26th 2023 I am getting this same error trying to join Regidrago AND Mega Tyranitar raids. So apparently they didn’t fix it permanently. Can ANYONE help here???
Same here error 2 times July 30th
Same message for EVERY remote raid I try for the last week.