i-83 Lagging

cinwie

hi.

sorry, I'm back again with the topic quadhost or i-83
already from 25/05/2019 (05:46) I open the ticket, but there is no reply at all
my ipv4 is very slow and my ipv6 can't connect, please for @quadhost or @i83 to fix it immediately.

thank you

SirFoxy

Pretty sure i83 is a known shit host.

Miky

I can confirm everything - on my side of course, pretty bad IPv4, not answering IPv6, and 2 weeks without even acknowledge on multiple tickets.

No surprise really, but even worse than expected!

teochristian

Seems to be ok on my end:

64 bytes from 103.216.223.11: icmp_seq=1 ttl=49 time=202 ms

teamacc

@teochristian said:
Seems to be ok on my end:

64 bytes from 103.216.223.11: icmp_seq=1 ttl=49 time=202 ms

That's the ip listed as "mrVM", not the company that's having issues.

i83

Issue with IPv4 loss and IPv6 connectivity is open with the upstream, awaiting resolution from there side.

Due to delays in response and resolution from their side we are evaluating moving upstreams as per the service announcement.

Apologies for any inconvenience caused by the upstream disruption.

teochristian

@teamacc said:

@teochristian said:
Seems to be ok on my end:

64 bytes from 103.216.223.11: icmp_seq=1 ttl=49 time=202 ms

That's the ip listed as "mrVM", not the company that's having issues.

You're right, sorry.

64 bytes from 111.221.44.154: icmp_seq=25 ttl=53 time=1546 ms
64 bytes from 111.221.44.154: icmp_seq=26 ttl=53 time=1752 ms
64 bytes from 111.221.44.154: icmp_seq=27 ttl=53 time=1598 ms

cinwie

Thank you @i83 for replying my ticket, after I posted it here.

cinwie

@teochristian said:

@teamacc said:

@teochristian said:
Seems to be ok on my end:

64 bytes from 103.216.223.11: icmp_seq=1 ttl=49 time=202 ms

That's the ip listed as "mrVM", not the company that's having issues.

You're right, sorry.

64 bytes from 111.221.44.154: icmp_seq=25 ttl=53 time=1546 ms
64 bytes from 111.221.44.154: icmp_seq=26 ttl=53 time=1752 ms
64 bytes from 111.221.44.154: icmp_seq=27 ttl=53 time=1598 ms

i just made a comparison between 2 sgp ip

skorous

cinwie said: Thank you @i83 for replying my ticket, after I posted it here.

Since that Service Announcement is from a week and a half ago and directly on point with your issue he likely figured you knew so responding wasn't critical.

cinwie

@skorous said:

cinwie said: Thank you @i83 for replying my ticket, after I posted it here.

Since that Service Announcement is from a week and a half ago and directly on point with your issue he likely figured you knew so responding wasn't critical.

the announcement they just made, I often visited the Network Status but never saw the announcement

skorous

cinwie said: I often visited the Network Status but never saw the announcement

Date - 22/05/2019 06:00

Click the link in i-83's post. Not to be a jerk, just don't like to see a host catch crap unjustifiably.

cinwie

@skorous said:

cinwie said: I often visited the Network Status but never saw the announcement

Date - 22/05/2019 06:00

Click the link in i-83's post. Not to be a jerk, just don't like to see a host catch crap unjustifiably.

I am lazy to argue with you, only the @i83 and God knows everything. thank you

ksfi8

I constantly checked the Network Status page when the problem started and can confirm that the announcement was not made at the timestamp. It was put up just a few days ago.

cinwie

@ksfi8 said:
I constantly checked the Network Status page when the problem started and can confirm that the announcement was not made at the timestamp. It was put up just a few days ago.

@skorous are you reading this?

AnthonySmith