bgpreport

Network · data from 2026-11-12

AS267219 NETWARE TELECOMUNICACOES E INFORMATICA EIRELI

Registry name: AS267219 - Netware Telecomunicacoes e Informatica EIRELI, BR · PeeringDB

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

Announced routes

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

204.157.132.0/23 No ROA Other IRR onlyRADB 672 100% 66
209.14.90.0/24 No ROA Other IRR onlyRADB 672 100% 67
2804:4a1c:c000::/36 Valid Nonecovered by 2804:4a1c::/32 636 100% 67
45.231.212.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
2804:4a1c::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:4a1c::/36 Valid Other IRR onlyRADB 634 100% 67
2804:4a1c::/37 Valid Other IRR onlyRADB 634 100% 67
2804:4a1c:800::/37 Valid Other IRR onlyRADB 634 100% 67
45.231.212.0/24 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
45.231.213.0/24 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS267219: AS267219:AS-NETWARE. 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 (AS267219 isn't in the set, or no route object for AS267219 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 objectsAS267219 in itNot covered
AS267219:AS-NETWARE TC 139 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 12 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none204.157.132.0/23No ROA covers it. Add a ROA for AS267219, maxLength 23.672 of 673
Route object: RIR204.157.132.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none209.14.90.0/24No ROA covers it. Add a ROA for AS267219, maxLength 24.672 of 673
Route object: RIR209.14.90.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2804:4a1c:c000::/36No route object for it. A route object for 2804:4a1c::/32 with origin AS267219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267219 in the RIR database for the space.636 of 636
Route object: RIR45.231.212.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:4a1c::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a1c::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a1c::/37Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a1c:800::/37Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR45.231.212.0/24Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR45.231.213.0/24Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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