bgpreport

Network · data from 2026-11-12

AS263256 PROVEDOR DE INTERNET EXTREMA

Registry name: AS263256 - PIX PROVEDOR DE INTERNET LTDA - ME, BR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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 AS263256, seen from no peer

Announced routes

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

198.58.8.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
198.58.10.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
170.247.200.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.200.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.200.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.201.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.202.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.202.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.247.203.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
198.58.8.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
198.58.11.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
198.58.8.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
2804:17e0::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:17e0::/33 Valid Other IRR onlyRADB, TC 631 99% 67
2804:17e0::/34 Valid Other IRR onlyTC 631 99% 67
2804:17e0:4000::/34 Valid Other IRR onlyTC 631 99% 67
2804:17e0:8000::/33 Valid Other IRR onlyTC 631 99% 67
2804:17e0:8000::/34 Valid Other IRR onlyTC 631 99% 67
2804:17e0:c000::/34 Valid Other IRR onlyTC 631 99% 67
198.58.9.0/24 Valid Other IRR onlyRADB, TC 128 19% 45
198.58.10.0/24 Valid Other IRR onlyRADB, TC 128 19% 45

AS-SET

AS263256'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 21 are in fix.csv.

  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
Route object: RIR198.58.8.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR198.58.10.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.247.200.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.200.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.200.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.201.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.202.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.202.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.247.203.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR198.58.8.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR198.58.11.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR198.58.8.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:17e0::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0:4000::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0:8000::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0:8000::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:17e0:c000::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR198.58.9.0/24Route object only in RADB, TC. Add it in the RIR database for the space.128 of 673
Route object: RIR198.58.10.0/24Route object only in RADB, TC. Add it in the RIR database for the space.128 of 673

Route objects not announced

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