bgpreport

Network · data from 2026-11-12

AS263858 RS NET

Registry name: AS263858 - RS NET EIRELI ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263858, 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.
138.186.48.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
138.186.48.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
138.186.50.0/23 Valid Other IRR onlyTC 671 100% 67
2804:26cc::/32 Valid Other IRR onlyRADB, TC 634 100% 69
2804:26cc::/33 Valid Other IRR onlyTC 634 100% 69
2804:26cc:8000::/33 Valid Other IRR onlyTC 634 100% 69
138.186.48.0/24 Valid Other IRR onlyRADB, TC 208 31% 56
138.186.49.0/24 Valid Other IRR onlyTC 208 31% 56
138.186.51.0/24 Valid Other IRR onlyTC 208 31% 56
138.186.50.0/24 Valid Other IRR onlyTC 207 31% 56

AS-SET

AS263858'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 10 are in fix.csv.

  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: RIR138.186.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.186.48.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.186.50.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:26cc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:26cc::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:26cc:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR138.186.48.0/24Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673
Route object: RIR138.186.49.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR138.186.51.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR138.186.50.0/24Route object only in TC. Add it in the RIR database for the space.207 of 673

Route objects not announced

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