bgpreport

Network · data from 2026-11-12

AS18933 USCC-MPLS01 - T-Mobile USA, Inc.

Registry name: USCC-MPLS01 - T-Mobile USA, Inc., US · not in PeeringDB

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

Announced routes

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

165.27.248.0/24 No ROA Other origin only 670 100% 67
166.181.160.0/20 No ROA None 670 100% 67
166.182.160.0/20 No ROA Other origin only 670 100% 67
166.224.192.0/19 No ROA None 670 100% 67
166.224.224.0/19 No ROA None 670 100% 67
198.227.57.0/24 No ROA Other origin only 670 100% 67
198.227.60.0/24 No ROA Other origin only 670 100% 67
198.227.61.0/24 No ROA Other origin only 670 100% 67
198.227.189.0/24 No ROA Other origin only 670 100% 67
198.227.238.0/24 No ROA Other origin only 670 100% 67
198.227.249.0/24 No ROA Other origin only 670 100% 67
165.27.253.0/24 No ROA Other origin only 667 99% 67
166.182.0.0/16 No ROA Other origin only 653 97% 67
165.27.240.0/22 No ROA None 650 97% 67

AS-SET

AS18933 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none14
ChangePrefix or setDetailFull-table peers
ROA: none165.27.248.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none165.27.248.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none166.181.160.0/20No ROA covers it. Add a ROA for AS18933, maxLength 20.670 of 673
Route object: none166.181.160.0/20No route object for it. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none166.182.160.0/20No ROA covers it. Add a ROA for AS18933, maxLength 20.670 of 673
Route object: none166.182.160.0/20Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none166.224.192.0/19No ROA covers it. Add a ROA for AS18933, maxLength 19.670 of 673
Route object: none166.224.192.0/19No route object for it. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none166.224.224.0/19No ROA covers it. Add a ROA for AS18933, maxLength 19.670 of 673
Route object: none166.224.224.0/19No route object for it. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.57.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.57.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.60.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.60.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.61.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.61.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.189.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.189.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.238.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.238.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none198.227.249.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.670 of 673
Route object: none198.227.249.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.670 of 673
ROA: none165.27.253.0/24No ROA covers it. Add a ROA for AS18933, maxLength 24.667 of 673
Route object: none165.27.253.0/24Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.667 of 673
ROA: none166.182.0.0/16No ROA covers it. Add a ROA for AS18933, maxLength 16.653 of 673
Route object: none166.182.0.0/16Route objects for it name AS198949. Add a route object with origin AS18933 in the RIR database for the space.653 of 673
ROA: none165.27.240.0/22No ROA covers it. Add a ROA for AS18933, maxLength 22.650 of 673
Route object: none165.27.240.0/22No route object for it. Add a route object with origin AS18933 in the RIR database for the space.650 of 673

Route objects not announced

Every route object with origin AS18933 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.