Vultr performance issues in Chicago
-
and issues
-
not even a console... wtf
-
@scottalanmiller said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
what's also weird - I didn't get any vultr emails about the issue.
I always get NJ emails. Time to dig into that I guess.
Are you running systems in the Chicago datacenter?
yes.
-
@jaredbusch said in Vultr performance issues in Chicago:
@syko24 said in Vultr performance issues in Chicago:
@scottalanmiller said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
what's also weird - I didn't get any vultr emails about the issue.
I always get NJ emails. Time to dig into that I guess.
Are you running systems in the Chicago datacenter?
Yes. And I know the phones being down for 30 mins is not a huge deal. Just wanted to see if you guys had a way to failover the phones if something like this happens.
I have the failover already setup at the provider level.
yeah, in my case that's not working much, because most calls are getting to the PBX, but there is a ton of dead air and dropped calls.
-
@jaredbusch said in Vultr performance issues in Chicago:
not even a console... wtf
This is what I was really afraid of - if you can't get access to Chicago, you can't push a backup to another DC, etc.
-
@dashrender said in Vultr performance issues in Chicago:
This is what I was really afraid of - if you can't get access to Chicago, you can't push a backup to another DC, etc.
You don't use the console to get a backup....
-
@jaredbusch said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
This is what I was really afraid of - if you can't get access to Chicago, you can't push a backup to another DC, etc.
You don't use the console to get a backup....
never said you did.
-
@dashrender said in Vultr performance issues in Chicago:
yeah, in my case that's not working much, because most calls are getting to the PBX, but there is a ton of dead air and dropped calls.
Yes, that is the issue with intermittent connectivity. usually up enough for the trunks not to be failed.
For me it was < 30 minutes for any one customer to be having issues.
Things seem to have normalized, but Vultr still has the issue open.
-
@dashrender said in Vultr performance issues in Chicago:
@jaredbusch said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
This is what I was really afraid of - if you can't get access to Chicago, you can't push a backup to another DC, etc.
You don't use the console to get a backup....
never said you did.
Except that was what you quoted.
The interface was functional. I did not try any other actions except to open the console.
-
@jaredbusch said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
yeah, in my case that's not working much, because most calls are getting to the PBX, but there is a ton of dead air and dropped calls.
Yes, that is the issue with intermittent connectivity. usually up enough for the trunks not to be failed.
For me it was < 30 minutes for any one customer to be having issues.
Things seem to have normalized, but Vultr still has the issue open.
And Chicago is marked cleared now.
-
@jaredbusch said in Vultr performance issues in Chicago:
@jaredbusch said in Vultr performance issues in Chicago:
@dashrender said in Vultr performance issues in Chicago:
yeah, in my case that's not working much, because most calls are getting to the PBX, but there is a ton of dead air and dropped calls.
Yes, that is the issue with intermittent connectivity. usually up enough for the trunks not to be failed.
For me it was < 30 minutes for any one customer to be having issues.
Things seem to have normalized, but Vultr still has the issue open.
And Chicago is marked cleared now.
I didn't see what it said before seeing the "resolved issues" at the top...
