bgpreport

Network · data from 2026-11-12

AS270478 AS270478 - CapitalNet MS

Registry name: AS270478 - CapitalNet MS, BR · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.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
35Route objects not announced registered with origin AS270478, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270478, 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.
200.106.128.0/24 No ROA Other IRR onlyRADB 670 100% 66
200.106.129.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:6c94::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS270478 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 41 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
ROA: none200.106.128.0/24No ROA covers it. Add a ROA for AS270478, maxLength 24.670 of 673
Route object: RIR200.106.128.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.106.129.0/24No ROA covers it. Add a ROA for AS270478, maxLength 24.670 of 673
Route object: RIR200.106.129.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:6c94::/32No ROA covers it. Add a ROA for AS270478, maxLength 32.634 of 636
Route object: RIR2804:6c94::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

200.106.128.0/22RADB, TCNo ROA
200.106.128.0/23RADBNo ROA
200.106.130.0/23RADBNo ROA
200.106.130.0/24RADBNo ROA
200.106.131.0/24RADBNo ROA
2804:6c94::/33RADBNo ROA
2804:6c94::/34RADBNo ROA
2804:6c94::/35RADBNo ROA
2804:6c94::/36RADBNo ROA
2804:6c94:1000::/36RADBNo ROA
2804:6c94:2000::/35RADBNo ROA
2804:6c94:2000::/36RADBNo ROA
2804:6c94:3000::/36RADBNo ROA
2804:6c94:4000::/34RADBNo ROA
2804:6c94:4000::/35RADBNo ROA
2804:6c94:4000::/36RADBNo ROA
2804:6c94:5000::/36RADBNo ROA
2804:6c94:6000::/35RADBNo ROA
2804:6c94:6000::/36RADBNo ROA
2804:6c94:7000::/36RADBNo ROA
2804:6c94:8000::/33RADBNo ROA
2804:6c94:8000::/34RADBNo ROA
2804:6c94:8000::/35RADBNo ROA
2804:6c94:8000::/36RADBNo ROA
2804:6c94:9000::/36RADBNo ROA
2804:6c94:a000::/35RADBNo ROA
2804:6c94:a000::/36RADBNo ROA
2804:6c94:b000::/36RADBNo ROA
2804:6c94:c000::/34RADBNo ROA
2804:6c94:c000::/35RADBNo ROA
2804:6c94:c000::/36RADBNo ROA
2804:6c94:d000::/36RADBNo ROA
2804:6c94:e000::/35RADBNo ROA
2804:6c94:e000::/36RADBNo ROA
2804:6c94:f000::/36RADBNo ROA

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.