bgpreport

Network · data from 2026-11-12

AS267469 W8 Telecom

Registry name: AS267469 - W8 Telecom Ltda - ME, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 25.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 AS267469, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267469, 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.
2804:41f8:f240::/43 Valid Nonecovered by 2804:41f8::/32 636 100% 67
2804:41f8:f004::/46 Valid Nonecovered by 2804:41f8::/32 635 100% 69
2804:41f8:f220::/43 Valid Nonecovered by 2804:41f8::/32 635 100% 69
192.141.156.0/24 Valid Other IRR onlyRADB 673 100% 67
192.141.156.0/22 Valid Other IRR onlyRADB 672 100% 66
192.141.157.0/24 Valid Other IRR onlyRADB 671 100% 66
192.141.158.0/24 Valid Other IRR onlyRADB 671 100% 66
192.141.159.0/24 Valid Other IRR onlyRADB 671 100% 66
2804:41f8::/32 Valid Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS267469: RADB::AS-W8TELECOM. 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 (AS267469 isn't in the set, or no route object for AS267469 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 objectsAS267469 in itNot covered
RADB::AS-W8TELECOM RADB12 member sets in no database: AS-267513, AS-269472, AS-RMS, AS-SNT-28604, AS266037:AS-ALL … 15272,238 Yes 0

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: none3
  • Route object: RIR6
  • AS-SET: missing member12
ChangePrefix or setDetailFull-table peers
Route object: none2804:41f8:f240::/43No route object for it. A route object for 2804:41f8::/32 with origin AS267469 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267469 in the RIR database for the space.636 of 636
Route object: none2804:41f8:f004::/46No route object for it. A route object for 2804:41f8::/32 with origin AS267469 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267469 in the RIR database for the space.635 of 636
Route object: none2804:41f8:f220::/43No route object for it. A route object for 2804:41f8::/32 with origin AS267469 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267469 in the RIR database for the space.635 of 636
Route object: RIR192.141.156.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.141.156.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR192.141.157.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.141.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.141.159.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:41f8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS-267513; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS-269472; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS-RMS; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS-SNT-28604; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS266037:AS-ALL; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS267507:AS-LHOST; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS268054:AS-CONE; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS269627:AS-EXAINTERNET; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS52600:AS-ANNOUNCEMENTS; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS52625:AS-ANNOUNCEMENTS; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS53175:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberRADB::AS-W8TELECOMAS-W8TELECOM (RADB) lists AS61616:AS-ALL; no IRR database read has it.

Route objects not announced

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