bgpreport

Network · data from 2026-11-12

AS4186 ATTIS-ASN4186 - AT&T Enterprises, LLC

Registry name: ATTIS-ASN4186 - AT&T Enterprises, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4186, 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.

12.96.44.0/24 No ROA None 673 100% 67
157.96.84.0/24 No ROA None 673 100% 67
157.96.85.0/24 No ROA None 673 100% 67
157.96.86.0/24 No ROA None 673 100% 67
2610:e8::/33 No ROA None 1 0%low visibility 1
2610:e8:8000::/33 No ROA None 1 0%low visibility 1

AS-SET

AS4186 isn't in PeeringDB, where networks name their 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 21 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none12.96.44.0/24No ROA covers it. Add a ROA for AS4186, maxLength 24.673 of 673
Route object: none12.96.44.0/24No route object for it. Add a route object with origin AS4186 in the RIR database for the space.673 of 673
ROA: none157.96.84.0/24No ROA covers it. Add a ROA for AS4186, maxLength 24.673 of 673
Route object: none157.96.84.0/24No route object for it. Add a route object with origin AS4186 in the RIR database for the space.673 of 673
ROA: none157.96.85.0/24No ROA covers it. Add a ROA for AS4186, maxLength 24.673 of 673
Route object: none157.96.85.0/24No route object for it. Add a route object with origin AS4186 in the RIR database for the space.673 of 673
ROA: none157.96.86.0/24No ROA covers it. Add a ROA for AS4186, maxLength 24.673 of 673
Route object: none157.96.86.0/24No route object for it. Add a route object with origin AS4186 in the RIR database for the space.673 of 673
ROA: none2610:e8::/33No ROA covers it. Add a ROA for AS4186, maxLength 33.1 of 636
Route object: none2610:e8::/33No route object for it. Add a route object with origin AS4186 in the RIR database for the space.1 of 636
ROA: none2610:e8:8000::/33No ROA covers it. Add a ROA for AS4186, maxLength 33.1 of 636
Route object: none2610:e8:8000::/33No route object for it. Add a route object with origin AS4186 in the RIR database for the space.1 of 636

Route objects not announced

Route objects with origin AS4186 whose prefix no peer sees AS4186 announce. Many are kept on purpose (backup routes, space announced only in some places).

165.110.0.0/16ARINValid
2602:fbdc::/48ARINValid
2602:fbdc:2::/48ARINValid
2602:fbdc:6::/48ARINValid
2602:fbdc:10::/48ARINValid
2602:fbdc:12::/48ARINValid
2602:fbdc:80::/48ARINValid
2602:fbdc:8d::/48ARINValid
2620:bf::/48ARINValid

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.