Posts tagged AT&T

AT&T Data outage in Wilmington, DE

Reported by: Brian Driscall

We are having problems in Wilmington, DE newer devices showing 3g (lower case), older devices showing edge (lower case).  Called at&t and they confirmed the outage with no ETA.

The ticket number is 11941794

AT&T: San Diego phone outages

AT&T just confirmed that there is a phone #outage currently being worked on in the San Diego area. This affects both voice and data,
preventing users from consistently being able to connect to the AT&T network to send/receive phone calls, text messages, and data.

Ticket number for the issue is #TT000010046283. No ETA for repair.

3-13-2009 AT&T, T•Mobile, Rogers and Verizon in the US and Canada BIS Latency

Reported by: “Bla1ze”

Ticket #: TT000009913115

What’s Happening?
Blackberry/RIM is experiencing an error within their network. BIS customers may experience delays or failures from their integrated accounts.

Action Taken
Blackberry RIM engineers are currently working to resolve the issue and expect to have a resolution soon.

EDIT: T•Mobile, Rogers and Verizon in the US and Canada are also included in this.

BIS Latency AT&T

TT# TT000009870340-

Customers accessing email or performing file transfer may experience latency or failure to connect message received on device.

Regions: Central, NorthEast, SouthEast, West.

Impact: BlackBerry Integrated Mail Service is unavailable for 69% of ATT BlackBerry Users of the Americas BIS 2.X.

NY Citywide Blackberry Outage AT&T

We’ve been informed of a City wide Blackberry outage with AT&T in NT.

From: xxxx
Sent: Wednesday, February 11, 2009 12:56 PM
Subject: Citywide Blackberry Outage

Wed Feb 11 12:51:51 2009
STATUS: Open – Active
PROGNOSIS: Monitoring
Utility-Blackberry Outage
Citywide
Possible AT&T blackberry outages to impact the New York City area.

Start Time: Feb 11 2009 06:30 AM PST

Symptoms you may experience: RIM Blackberry users may be unable to
send/receive messages or may have difficulty connecting to the network.

Estimated time of repair is unknown and technicians are working towards a
resolution as quickly as possible.
OEM Watch Command will advise as necessary.

Can anyone confirm they are seeing the same issue? Reply below if so.