bgpreport

Network · data from 2026-11-12

AS53873 SCL-550-53873 - SATC COLO LLC

Registry name: SCL-550-53873 - SATC COLO LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53873, 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.
64.132.4.0/22 No ROA Other IRR onlyRADB 673 100% 67
74.203.251.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.203.171.0/24 No ROA RIR databaseARIN 672 100% 67
97.77.87.0/24 Valid Other IRR onlyRADB 673 100% 67
2604:520::/32 Valid RIR databaseARIN 636 100% 67

AS-SET

AS53873 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 12 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none64.132.4.0/22No ROA covers it. Add a ROA for AS53873, maxLength 22.673 of 673
Route object: RIR64.132.4.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.203.251.0/24No ROA covers it. Add a ROA for AS53873, maxLength 24.672 of 673
Route object: RIR74.203.251.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.203.171.0/24No ROA covers it. Add a ROA for AS53873, maxLength 24.672 of 673
Route object: RIR97.77.87.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

64.132.4.0/24RADBNo ROA
64.132.5.0/24RADBNo ROA
64.132.6.0/24RADBNo ROA
64.132.7.0/24RADBNo ROA
74.203.241.0/24RADBNo ROA
155.103.126.0/23ARINValid

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.