bgpreport

Network · data from 2026-11-12

AS268526 Conect Virtua Provedor de Internet Banda Larga

Registry name: AS268526 - Conect Virtua Provedor de Internet Banda Larga, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268526, 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:5290::/34 Valid Nonecovered by 2804:5290::/33 634 100% 67
2804:5290:4000::/34 Valid Nonecovered by 2804:5290::/33 634 100% 67
2804:5290:8000::/34 Valid Nonecovered by 2804:5290:8000::/33 634 100% 67
2804:5290:c000::/34 Valid Nonecovered by 2804:5290:8000::/33 634 100% 67
45.162.29.0/24 Valid Other IRR onlyRADB 672 100% 66
45.162.31.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
45.162.28.0/24 Valid Other IRR onlyRADB 669 99% 67
45.162.30.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 66
2804:5290::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:5290::/33 Valid Other IRR onlyTC 635 100% 69
2804:5290:8000::/33 Valid Other IRR onlyTC 635 100% 69
45.162.28.0/23 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

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

  • Route object: none4
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:5290::/34No route object for it. A route object for 2804:5290::/33 with origin AS268526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268526 in the RIR database for the space.634 of 636
Route object: none2804:5290:4000::/34No route object for it. A route object for 2804:5290::/33 with origin AS268526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268526 in the RIR database for the space.634 of 636
Route object: none2804:5290:8000::/34No route object for it. A route object for 2804:5290:8000::/33 with origin AS268526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268526 in the RIR database for the space.634 of 636
Route object: none2804:5290:c000::/34No route object for it. A route object for 2804:5290:8000::/33 with origin AS268526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268526 in the RIR database for the space.634 of 636
Route object: RIR45.162.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.162.31.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.162.28.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.162.30.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5290::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5290::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5290:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.162.28.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS268526 whose prefix no peer sees AS268526 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.162.28.0/22RADB, TCValid
2804:5290:400::/46TCValid

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.