ISP technical support contacts needed

[fdsa]

Do you know anyone working at ISPs as a network engineer/sysadmin? I'm currently experiencing big problems with AIS but would love to get contacts for other providers too, just in case.

I need real technical support who knows what "traceroute" or "BGP" is, not the usual telephone girls "please try to reboot your router ka"

[RedBackman]

https://xkcd.com/806/

 

Honestly great question and good luck. From my experience Thailand ISP tech support doesn't seem to escalate a home user ticket at all until they've physically sent someone to your house. They'll come cycle your router and check the lines first even if you can spell out the problem for them.

[fdsa]

28 minutes ago, RedBackman said:

https://xkcd.com/806/

 

Back at home I had the luxury of having the direct mobile phone number of one of the ISP's sysadmins, after I succeeded in convincing the phone girl that I know my sh.t and that the problem is on their side not with my router.

I wonder how Thai technicians would resolve the connectivity problem somewhere between Bangkok and Paris, by rebooting my router.

 

[recom273]

This is really frustrating. 

 

I was going to move to AIS until I found out I couldn't contact ISP support.

 

Sorry, its not much help to you, but 3BB do have a proper support who will check routes and connectivity on their end and can use anydesk to view any issue from your end. The one guy speakes English really well, when I have had issues in the past, he's offered solutions to issues that weren't necessarily 3BBs fault. I dont have his personal number, but you can always get a callback within a working day. So this kind of support does exist in Thailand, just difficult with AIS.

[fdsa]

AIS is dead again, 85% packet loss between AIS Bangkok and Hurricane Electric Singapore ????

 

I've grepped RIPE database for @ais.co.th and found a few email addresses, will try to contact them.

[Roger That]

It was a couple of years ago but I once contacted AIS fibre support via Twitter about a fairly technical issue and got someone who knew what they were talking about, could be worth a go?

https://twitter.com/aisfibrehelp

 

[fdsa]

still 85% packet loss between 49.231.70.51 AIS, Bangkok and 184.104.210.173 Hurricane Electric, Singapore.

and still no answer from
- [email protected]

- [email protected]

- [email protected]

 

I think I'll have to register in Twitter or Facebook ???? but meanwhile will try to contact [email protected], just in case

[fdsa]

BTW,

 

1 minute ago, fdsa said:

and still no answer from
- [email protected]

makes AIS a perfect hosting/ISP for cybercriminals LOL

[fdsa]

 

 

 

 

 

(that's 1gbps server in France)

[fdsa]

Wow, traffic from Thailand to Russia goes through America.

 

a cyber war in progress?

[fdsa]

The problem still persists after 9 months I've first reported it.

I've contacted the next hop in the traceroute (Hurricane Electric) but they replied something like "we are aware of the issue, waiting for the other party to fix it", so this problem is never going to be fixed because TiT.

So if you need a stable Internet access to European servers I suggest to use another internet provider, for example DTAC.

[fdsa]

AIS blocks all connections to github.com ????‍♂️ what a bs isp

[topt]

19 minutes ago, fdsa said:

AIS blocks all connections to github.com ????‍♂️ what a bs isp

That is scary......

No problem with True (github that is.....)

[NextG]

2 hours ago, fdsa said:

AIS blocks all connections to github.com ????‍♂️ what a bs isp

Are you sure?

[spongeworthy]

2 hours ago, fdsa said:

AIS blocks all connections to github.com ????‍♂️ what a bs isp

I'm sure you can find some sr network engineers in the usual places. If you're don't work for an ISP or other org with a large network and are unsure where to look, PM me and I'll point you in the right direction. Just keep in mind these aren't places to air your grievances with an ISP, these are where ISPs and the like communicate to resolve and discuss issues and other matters.

[fdsa]

38 minutes ago, spongeworthy said:

I'm sure you can find some sr network engineers in the usual places. If you're don't work for an ISP or other org with a large network and are unsure where to look, PM me and I'll point you in the right direction. Just keep in mind these aren't places to air your grievances with an ISP, these are where ISPs and the like communicate to resolve and discuss issues and other matters.

If you mean a mailing list like NANOG then there is a zero chance I'll find help there, because AIS ignores all emails even from their upstream:

On 2/12/2023 at 12:56 PM, fdsa said:

I've contacted the next hop in the traceroute (Hurricane Electric) but they replied something like "we are aware of the issue, waiting for the other party to fix it", so this problem is never going to be fixed because TiT.

but if not a mailing list then I'm all ears.

[fdsa]

1 hour ago, NextG said:

Are you sure?

Probably we have different AISes ????‍♂️

sh-4.4$ curl ifconfig.me/ip; echo
182.232.10.49
sh-4.4$ whob 182.232.10.49|grep -i org
AS-Org-Name: Advance Wireless Network
Org-Name: Assign for AIS_Internet Customers
sh-4.4$ host -t a github.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

github.com has address 20.205.243.166

sh-4.4$ ping -c 4 20.205.243.166
PING 20.205.243.166 (20.205.243.166) 56(84) bytes of data.

--- 20.205.243.166 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3078ms

sh-4.4$ curl -v https://20.205.243.166 --header 'Host: github.com'
*   Trying 20.205.243.166:443...
^C
sh-4.4$ curl --connect-timeout 5  -v https://20.205.243.166 --header 'Host: github.com'
*   Trying 20.205.243.166:443...
* After 5000ms connect time, move on!
* connect to 20.205.243.166 port 443 failed: Connection timed out
* Connection timeout after 5000 ms
* Closing connection 0
curl: (28) Connection timeout after 5000 ms

 

Everything else except Github works well (except 90% packet loss to my servers in France and Netherlands of course).

 

 

Edit: rebooting the modem (i.e. getting a new IP) fixed the issue, so - thanks for the idea.

Github works well with IP from 182.232.11.0/24