#chad_error
latent pebbleBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1400938193188032612
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ebon storm
Hello
steep haven
Can you share what you're seeing in DownDetector?
ebon storm
Per one of the campgrounds: "They couldn't pull up the Stripe.com Dashboard with their campground connection/wifi page starts to load but then says 'unavailable'"
They're having trouble processing payments or even accessing their dashboard, and it has been multiple locations in the same areas being reported on down detector
steep haven
What time was this photo taken?
ebon storm
checking with support, one second
11:45 Mountain Time
It sounds like some payments are finally starting to trickle through, however, they still cannot connect to the dashboard. Working on getting you more details on that as well
steep haven
Let me double check.
minor harbor
Hello, looking in to this. Do you have the serial numbers of any of the effected Terminals? I'm trying to find if we had a report like this, but it can sometimes be easier to work backwards from a specific case.
ebon storm
Let me see if I can get it for you
Here's the error from the dashboard when they attempt to access it
while waiting on the serial number
minor harbor
Thank you, I actually think I've found it. Catching up still and will report back in a minute
Do you know if any of your people are still seeing this issue? In the report I am looking at, there was a service disruption from an upstream partner that effected Google Fiber users mostly in the Salt Lake City area from 8:30 AM to 1:43 PM MT. It should be resolved now but if you are still seeing it I can escalate to my colleagues
ebon storm
Checking
latent pebbleBOT
ebon storm
As of 2:50 MT they were still unable to access dashboard.stripe.com
However payments starting going through. Our support lines have quieted down significantly
minor harbor
Gotcha, and do you know roughly where they were when that happened? Also can you send me your account ID? (acct_1234)
minor harbor
No worries, was able to find the right one. Do you happen to know the ID of the connected account that reported this? The regions we've checked look to be completely recovered so far. If they can try again now, it should succeed but I'm happy to check more of what we can see from our side.
ebon storm
Per support, I believe all is well now. Thank you very much for digging into this for me and determining a root cause. I believe the fiber disruption to be the culprit. Have a great weekend!