An easy way to prove it.
Write a script to Ping & TraceRoute via multiple VPN's, dump the results to a log file, & repeat itself every ~10 minutes throughout the day.
If you get crap/no connections from a direct connect attempt, but decent/any connection from the VPN endpoints, then the target knows that what their status page claims for your supposedly available status is a lie.
Example: if your local ISP is sending your entirely local signal on a ~300 mile round trip before coming back to the entirely local server, you can use the log to prove that fact, then to beat them with that fact to rip & rebuild a proper local circuit.
AWS can claim what they want, but a simple Ping+TraceRoute script run every few minutes for a few (days/weeks/months) will prove their claims as utter hogwash.
I did this to prove to my ISP that they were blowing smoke up my arse as far as signal degredation was concerned, so if they didn't do an R&R to establish a proper *entirely local* connection to the servers located in my own damned town (rather than the 300+ mile round trip the script proved), I'd use that as proof by which to complain to the various government agencies about the ISP's incompetence/fraud.
Two days later I had a proper local connection.
If you're having problems with $Provider claiming to be available when you can't reach them, consider running a Ping+TraceRoute>LogFile.txt for a few days to generate the evidence you need to beat them with a ClueBy4. =-J