bgpreport

Network · data from 2026-11-12

AS3555 AT&T Technical Services

Registry name: ATS-NET - AT&T Technical Services Company, Inc., US · PeeringDB

12IPv4 routes 91.7% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 12 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS3555, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3555, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
192.246.37.0/24 No ROA None 673 100% 67
192.31.9.0/24 Valid None 673 100% 67
198.17.99.0/24 Valid None 673 100% 67
198.22.152.0/24 Valid None 673 100% 67
198.137.234.0/23 Valid None 673 100% 67
199.74.244.0/24 Valid None 673 100% 67
199.79.216.0/24 Valid None 673 100% 67
199.89.132.0/23 Valid None 673 100% 67
199.89.158.0/23 Valid None 673 100% 67
199.89.160.0/24 Valid None 673 100% 67
204.89.153.0/24 Valid None 673 100% 67
204.89.154.0/24 Valid None 673 100% 67

AS-SET

AS3555's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: none1
  • Route object: none12
ChangePrefix or setDetailFull-table peers
ROA: none192.246.37.0/24No ROA covers it. Add a ROA for AS3555, maxLength 24.673 of 673
Route object: none192.246.37.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none192.31.9.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none198.17.99.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none198.22.152.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none198.137.234.0/23No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none199.74.244.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none199.79.216.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none199.89.132.0/23No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none199.89.158.0/23No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none199.89.160.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none204.89.153.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673
Route object: none204.89.154.0/24No route object for it. Add a route object with origin AS3555 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS3555 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.