We have a few circuits with ATT and a few VZ. Since friday we have seen
serveral intermittent issues throught ATT to reach various customers and our
various remote offices. If we swing the traffic through VZ interfaces using
static routes we can reach those locations fine. We were doing traceroutes
during the issue and we saw the traceroutes dying inside ATT network. I was
wondering if any one else saw similar issues ? On friday we saw issue
between ATT and GBLX peering point. We saw similar issue on tuesday. And
another one today.
We sent to ATT various traceroutes and opened a few tickets but didnt really
get any kind of confirmation. The problem seems to remedy itself on its own
after 10-30 minutes.
Please chime in if any one else saw similar issues transiting through AT&T
or global crossing.
Veerender Attri wrote:
We have a few circuits with ATT and a few VZ. Since friday we have seen
serveral intermittent issues throught ATT to reach various customers and our
various remote offices.
[snip]
Please chime in if any one else saw similar issues transiting through AT&T
or global crossing.
We have seen some strange routing issues while going through ATT as
well. Couldn't reach our MX office (VPN) for several hours on 2
occasions last week. The problem was indeed AT&T routing. As we're not a
customer of AT&T, I don't have much more info.
phil
And the Saga continues. We had issues reaching Taiwan through ATT today and
no issues if i flip the outbound traffic through Verizon. I called and
opened ticket with ATT and it seems like they dont want to help or even look
into the issue, its really getting frustrating. These intermittent issues
with ATT backbone routing has been going on for more than a week now. It
seems their Backbone wont converge for routing issues when they have issues
with their peering partners.
V