bgpreport

Network · data from 2026-11-12

AS268434 Quadri Telecom

Registry name: AS268434 - QUADRI TELECOM LTDA - ME, BR · PeeringDB

7IPv4 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 AS268434, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268434, 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.
45.160.236.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
45.160.236.0/23 Valid Other IRR onlyRADB 669 99% 67
45.160.238.0/23 Valid Other IRR onlyRADB 669 99% 67
2804:5128::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:5128::/34 Valid Other IRR onlyRADB 635 100% 67
2804:5128:4000::/34 Valid Other IRR onlyRADB 635 100% 67
2804:5128:8000::/33 Valid Other IRR onlyRADB 635 100% 67
2804:5128::/33 Valid Other IRR onlyRADB 634 100% 67
2804:5128:8000::/34 Valid Other IRR onlyRADB 352 55% 65
2804:5128:c000::/34 Valid Other IRR onlyRADB 352 55% 65
45.160.236.0/24 Valid Other IRR onlyRADB 206 31% 56
45.160.237.0/24 Valid Other IRR onlyRADB 206 31% 56
45.160.238.0/24 Valid Other IRR onlyRADB 206 31% 56
45.160.239.0/24 Valid Other IRR onlyRADB 206 31% 56

AS-SET

AS268434'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 14 are in fix.csv.

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR45.160.236.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.160.236.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.160.238.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5128::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5128::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5128:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5128:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5128::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:5128:8000::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:5128:c000::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR45.160.236.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673
Route object: RIR45.160.237.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673
Route object: RIR45.160.238.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673
Route object: RIR45.160.239.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673

Route objects not announced

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