bgpreport

Network · data from 2026-11-12

AS269566 PHI TELECOM

Registry name: AS269566 - PHI TELECOM LTDA.ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269566, 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.188.8.0/22 Valid Other IRR onlyTC 669 99% 67
45.188.8.0/23 Valid Other IRR onlyTC 669 99% 67
45.188.8.0/24 Valid Other IRR onlyTC 669 99% 67
45.188.9.0/24 Valid Other IRR onlyTC 669 99% 67
45.188.10.0/23 Valid Other IRR onlyTC 669 99% 67
45.188.10.0/24 Valid Other IRR onlyTC 669 99% 67
45.188.11.0/24 Valid Other IRR onlyTC 669 99% 67
2804:6688::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:6688::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:71::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:73::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:81::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:91::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:100::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:1071::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:1073::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:1081::/48 Valid Other IRR onlyRADB 633 100% 67
2804:6688:1091::/48 Valid Other IRR onlyRADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS269566: TC::AS269566. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS269566 isn't in the set, or no route object for AS269566 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS269566 in itNot covered
TC::AS269566 A single AS number, not a set: AS269566 (this network), 18 route objects.

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

  • Route object: RIR18
ChangePrefix or setDetailFull-table peers
Route object: RIR45.188.8.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.8.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.8.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.9.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.10.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.10.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.11.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:6688::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:71::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:73::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:81::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:91::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:100::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:1071::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:1073::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:1081::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:6688:1091::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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