bgpreport

Network · data from 2026-11-12

AS267566 AS267566 - Quality Telecom

Registry name: AS267566 - Quality Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267566, 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.70.65.0/24 Valid Nonecovered by 45.70.64.0/23 129 19% 43
45.70.66.0/24 Valid Nonecovered by 45.70.66.0/23 129 19% 43
45.70.67.0/24 Valid Nonecovered by 45.70.66.0/23 129 19% 43
45.70.64.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.70.64.0/23 Valid Other IRR onlyRADB 671 100% 66
45.70.66.0/23 Valid Other IRR onlyRADB 671 100% 66
2804:4360::/32 Valid Other IRR onlyRADB, TC 632 99% 67
45.70.64.0/24 Valid Other IRR onlyRADB 126 19% 42

AS-SET

AS267566 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 8 are in fix.csv.

  • Route object: none3
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
Route object: none45.70.65.0/24No route object for it. A route object for 45.70.64.0/23 with origin AS267566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267566 in the RIR database for the space.129 of 673
Route object: none45.70.66.0/24No route object for it. A route object for 45.70.66.0/23 with origin AS267566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267566 in the RIR database for the space.129 of 673
Route object: none45.70.67.0/24No route object for it. A route object for 45.70.66.0/23 with origin AS267566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267566 in the RIR database for the space.129 of 673
Route object: RIR45.70.64.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.70.64.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.70.66.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4360::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR45.70.64.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673

Route objects not announced

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