bgpreport

Network · data from 2026-11-12

AS269014 VIVEZA TELECOM AS269014

Registry name: AS269014 - ALLNET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269014, 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:5e24::/33 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24::/34 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:2000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:4000::/34 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:4000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:6000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:8000::/33 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:8000::/34 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:8000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:a000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:c000::/34 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:c000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24:e000::/35 Valid Nonecovered by 2804:5e24::/32 350 55% 65
2804:5e24::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:1000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:2000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:3000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:4000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:5000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:6000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:7000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:8000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:9000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:a000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:b000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:c000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:d000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:e000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
2804:5e24:f000::/36 Valid Nonecovered by 2804:5e24::/32 329 52% 65
45.176.220.0/24 Valid Nonecovered by 45.176.220.0/23 130 19% 45
45.176.221.0/24 Valid Nonecovered by 45.176.220.0/23 130 19% 45
45.176.222.0/24 Valid Nonecovered by 45.176.220.0/22 130 19% 45
45.176.223.0/24 Valid Nonecovered by 45.176.220.0/22 130 19% 45
45.176.222.0/23 Valid Nonecovered by 45.176.220.0/22 119 18% 44
45.176.220.0/22 Valid Other IRR onlyALTDB, RADB, TC 665 99% 67
2804:5e24::/32 Valid Other IRR onlyALTDB, RADB, TC 629 99% 67
45.176.220.0/23 Valid Other IRR onlyRADB 119 18% 44

AS-SET

PeeringDB's irr_as_set for AS269014: AS269014. 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 (AS269014 isn't in the set, or no route object for AS269014 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 objectsAS269014 in itNot covered
AS269014 A single AS number, not a set: AS269014 (this network), 3 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 38 are in fix.csv.

  • Route object: none35
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2804:5e24::/33No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24::/34No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:2000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:4000::/34No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:4000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:6000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:8000::/33No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:8000::/34No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:8000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:a000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:c000::/34No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:c000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24:e000::/35No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.350 of 636
Route object: none2804:5e24::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:1000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:2000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:3000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:4000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:5000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:6000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:7000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:8000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:9000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:a000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:b000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:c000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:d000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:e000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none2804:5e24:f000::/36No route object for it. A route object for 2804:5e24::/32 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.329 of 636
Route object: none45.176.220.0/24No route object for it. A route object for 45.176.220.0/23 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.130 of 673
Route object: none45.176.221.0/24No route object for it. A route object for 45.176.220.0/23 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.130 of 673
Route object: none45.176.222.0/24No route object for it. A route object for 45.176.220.0/22 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.130 of 673
Route object: none45.176.223.0/24No route object for it. A route object for 45.176.220.0/22 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.130 of 673
Route object: none45.176.222.0/23No route object for it. A route object for 45.176.220.0/22 with origin AS269014 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269014 in the RIR database for the space.119 of 673
Route object: RIR45.176.220.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:5e24::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR45.176.220.0/23Route object only in RADB. Add it in the RIR database for the space.119 of 673

Route objects not announced

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