[AusNOG] Curly One
Joseph Goldman
joseph at goldman.id.au
Thu Sep 26 15:43:40 AEST 2024
They would say that, as if 99.999% of people are working but a few
outliers are having issues then they'd not want to spend the time
deep-diving logs.
Shaun's findings are spot on - and i'd be confirming you are seeing the
same, that you get a valid response to the original request and that you
are getting similar error (403) for that resource which would indicate
it definitely IS a website issue, but it'll be up to them to tell you
why they are denying it. Perhaps superloop got a new block of IPs that
are flagged in the GeoIP DB they use? Have you seen a correlation with
the users assigned public IP such as are they all in the same
subnet/supernet block? Would definitely explain why same laptop works on
some internet connections but not on others, still without it being a
direct network issue.
Perhaps reach out to the site again with a src IP, datetime and the
resource thats getting 403'd (with a snapshot of request/response
headers) so they might be able to actually go log hunting for you.
------ Original Message ------
From: "TWIG Solutions" <sales at twig.com.au>
To: "AusNOG at lists.ausnog.net" <AusNOG at lists.ausnog.net>
Sent: 26/09/2024 3:29:59 PM
Subject: Re: [AusNOG] Curly One
>
> They have said there is no issue on the website end..
>
>
>
>
>On 26/09/2024 14:35, Nathan Brookfield wrote:
>>What do the backend website owners AXS and Cloudflare have to say, I’d
>>strongly suggest if your get a white page it’s nothing to do with the
>>ISP’s you mentioned, also it loads fine here on all of the networks I
>>manage.
>>
>>
>>
>>From: AusNOG <ausnog-bounces at lists.ausnog.net>
>><mailto:ausnog-bounces at lists.ausnog.net> on behalf of TWIG Solutions
>><sales at twig.com.au> <mailto:sales at twig.com.au>
>>Date: Thursday, 26 September 2024 at 14:19
>>To: AusNOG at lists.ausnog.net<AusNOG at lists.ausnog.net>
>><mailto:AusNOG at lists.ausnog.net>
>>Subject: [AusNOG] Curly One
>>
>>Afternoon All,
>> I have an issue with some of my clients, which I discovered while
>>looking into the issue for 1 client. After testing from various
>>other geographically and ISP diverse clients I discovered it's pretty
>>wide spread issue.
>>
>>The issue is that the website below will only display a blank white
>>page for most clients, definitely ALL clients (I have tested) using
>>Exetel/Superloop FTTN, FTTC and select FTTP.
>>
>>https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>>
>>Yet some clients, when they view the site on the same laptop when at
>>home (Telstra), it loads fine and shows a login page. They come back
>>to the office, and it wont. My own service when it was FTTC, didnt
>>work, now I am FTTP it works.
>>
>>I did some tracing and discovered that as soon as the data traverse a
>>certain link, it fails. I passed all my findings to
>>Exetel/Superloop technical and it's been now been in hand since
>>25/6/24 and revived again on 26/8/24 (after the original ticket was
>>closed with no resolution). Nor they are saying its a website issue,
>>and they suggested installing a CORs extension on Chrome as it "fixed"
>>it for them. Not a secure solution, but I tested extension on 3
>>clients, still no good, and why only for some clients??.
>>
>>So again I am waiting for responses, and the initial client who
>>reported to me is getting very p*ssed off with the delays. They use
>>the site a lot booking tickets for their clients etc...
>>
>>Traces shown below, I wonder if anyone can test and advise, perhaps
>>look at the traces you get if it does or doesn't work, as it seem
>>Exetel/Superloop are stumped.
>>
>>
>>Cheers,
>>
>>Mal
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>My Service Working
>>Service: 1000/50 FTTP
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
>>[172.64.151.20]
>>over a maximum of 30 hops:
>>
>> 1 <1 ms <1 ms <1 ms [redacted]
>> 2 4 ms 3 ms 4 ms [redacted]
>> 3 2 ms 2 ms 2 ms 202.90.206.198
>> 4 3 ms 3 ms *
>>Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]
>> 5 3 ms 4 ms 8 ms 27.122.122.15
>> 6 4 ms 6 ms 3 ms 108.162.247.77
>> 7 3 ms 3 ms 3 ms 172.64.151.20
>>
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>Client 1 Not Working
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
>>[2606:4700:4400::6812:24ec]
>>over a maximum of 30 hops:
>>
>> 1 * * * Request timed out.
>> 2 * * * Request timed out.
>> 3 10 ms 10 ms 10 ms [redacted]
>> 4 * * 11 ms r0q86sqz1y5z2lmg941.ip6.superloop.au
>>[2401:d000:3401::31]
>> 5 * 10 ms *
>>bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
>>[2401:d000:10:100::2c1]
>> 6 32 ms 13 ms 24 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au
>>[2401:d000:3202::12]
>> 7 10 ms 10 ms 10 ms 2400:cb00:26:3::
>> 8 10 ms 10 ms 10 ms 2606:4700:4400::6812:24ec
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Initial Client - NOT WORKING
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
>>[2606:4700:4400::6812:24ec]
>>over a maximum of 30 hops:
>>
>> 1 * * * Request timed out.
>> 2 * * * Request timed out.
>> 3 9 ms 9 ms 9 ms 2406:3400:0:1::1
>> 4 * * * Request timed out.
>> 5 9 ms 9 ms *
>>bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
>>[2401:d000:10:100::2c1]
>> 6 17 ms 24 ms 21 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au
>>[2401:d000:3202::12]
>> 7 10 ms 9 ms 9 ms 2400:cb00:491:3::
>> 8 9 ms 9 ms 9 ms 2606:4700:4400::6812:24ec
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Client 2 Not Working
>>
>>Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with
>>32 bytes of data:
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>
>>Ping statistics for 172.64.151.20:
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>>Approximate round trip times in milli-seconds:
>> Minimum = 13ms, Maximum = 13ms, Average = 13ms
>>
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
>>[172.64.151.20]
>>over a maximum of 30 hops:
>>
>> 1 <1 ms <1 ms <1 ms [redacted]
>> 2 12 ms 12 ms 12 ms [redacted]
>> 3 13 ms 13 ms 13 ms 10.1.23.54 [10.1.23.54]
>> 4 13 ms 13 ms 12 ms
>>Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com
>>[116.255.21.108]
>> 5 13 ms * 13 ms
>>Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
>> 6 13 ms 13 ms 14 ms 27.122.122.15
>> 7 14 ms 13 ms 13 ms 108.162.250.5
>> 8 13 ms 13 ms 13 ms 172.64.151.20
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Client 3 Not Working
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
>>[104.18.36.236]
>>over a maximum of 30 hops:
>>
>> 1 <1 ms <1 ms <1 ms [redacted]
>> 2 1 ms 2 ms 1 ms [redacted]
>> 3 2 ms 2 ms 2 ms 10.1.21.186
>> 4 2 ms 2 ms 1 ms
>>Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com
>>[116.255.21.108]
>> 5 2 ms 1 ms 2 ms
>>Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
>> 6 3 ms 2 ms 5 ms 27.122.122.15
>> 7 3 ms 3 ms 2 ms 108.162.247.83
>> 8 3 ms 2 ms 2 ms 104.18.36.236
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/de3f29b5/attachment-0001.htm>
More information about the AusNOG
mailing list