bgpreport

Network · data from 2026-11-12

AS265207 PLUS PROVEDOR DE INTERNET

Registry name: AS265207 - PLUS PROVEDOR DE INTERNET LTDA - ME, BR · PeeringDB

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

Announced routes

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

179.0.68.0/23 Valid Nonecovered by 179.0.68.0/22 126 19% 44
179.0.70.0/23 Valid Nonecovered by 179.0.68.0/22 126 19% 44
2804:2c44::/34 Valid Nonecovered by 2804:2c44::/33 110 17% 43
2804:2c44:4000::/34 Valid Nonecovered by 2804:2c44::/33 110 17% 43
2804:2c44:8000::/34 Valid Nonecovered by 2804:2c44:8000::/33 110 17% 43
2804:2c44:c000::/34 Valid Nonecovered by 2804:2c44:8000::/33 110 17% 43
187.86.16.0/22 Valid Other IRR onlyALTDB 673 100% 67
179.0.68.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
167.250.160.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
167.250.160.0/23 Valid Other IRR onlyALTDB 671 100% 67
187.86.16.0/23 Valid Other IRR onlyALTDB 671 100% 67
187.86.18.0/23 Valid Other IRR onlyALTDB 670 100% 67
2804:2c44::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:2c44::/33 Valid Other IRR onlyALTDB 633 100% 67
2804:2c44:8000::/33 Valid Other IRR onlyALTDB 633 100% 67
167.250.162.0/23 Valid Other IRR onlyALTDB 126 19% 44
167.250.160.0/24 Valid Other IRR onlyALTDB, RADB 69 10% 33
167.250.161.0/24 Valid Other IRR onlyALTDB, RADB 69 10% 33
167.250.162.0/24 Valid Other IRR onlyALTDB, RADB 69 10% 33
167.250.163.0/24 Valid Other IRR onlyALTDB, RADB 69 10% 33
179.0.68.0/24 Valid Other IRR onlyRADB 69 10% 33
179.0.69.0/24 Valid Other IRR onlyRADB 69 10% 33
179.0.70.0/24 Valid Other IRR onlyRADB 69 10% 33
179.0.71.0/24 Valid Other IRR onlyRADB 69 10% 33
187.86.16.0/24 Valid Other IRR onlyALTDB 65 10%low visibility 32
187.86.17.0/24 Valid Other IRR onlyALTDB 65 10%low visibility 32
187.86.18.0/24 Valid Other IRR onlyALTDB 65 10%low visibility 32
187.86.19.0/24 Valid Other IRR onlyALTDB 65 10%low visibility 32

AS-SET

PeeringDB's irr_as_set for AS265207: AS-265207. 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 (AS265207 isn't in the set, or no route object for AS265207 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 objectsAS265207 in itNot covered
AS-265207 ALTDB 102143 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 28 are in fix.csv.

  • Route object: none6
  • Route object: RIR22
ChangePrefix or setDetailFull-table peers
Route object: none179.0.68.0/23No route object for it. A route object for 179.0.68.0/22 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.126 of 673
Route object: none179.0.70.0/23No route object for it. A route object for 179.0.68.0/22 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.126 of 673
Route object: none2804:2c44::/34No route object for it. A route object for 2804:2c44::/33 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.110 of 636
Route object: none2804:2c44:4000::/34No route object for it. A route object for 2804:2c44::/33 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.110 of 636
Route object: none2804:2c44:8000::/34No route object for it. A route object for 2804:2c44:8000::/33 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.110 of 636
Route object: none2804:2c44:c000::/34No route object for it. A route object for 2804:2c44:8000::/33 with origin AS265207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265207 in the RIR database for the space.110 of 636
Route object: RIR187.86.16.0/22Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: RIR179.0.68.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR167.250.160.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR167.250.160.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.86.16.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.86.18.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2c44::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2c44::/33Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2c44:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR167.250.162.0/23Route object only in ALTDB. Add it in the RIR database for the space.126 of 673
Route object: RIR167.250.160.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR167.250.161.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR167.250.162.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR167.250.163.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR179.0.68.0/24Route object only in RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR179.0.69.0/24Route object only in RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR179.0.70.0/24Route object only in RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR179.0.71.0/24Route object only in RADB. Add it in the RIR database for the space.69 of 673
Route object: RIR187.86.16.0/24Route object only in ALTDB. Add it in the RIR database for the space.65 of 673
Route object: RIR187.86.17.0/24Route object only in ALTDB. Add it in the RIR database for the space.65 of 673
Route object: RIR187.86.18.0/24Route object only in ALTDB. Add it in the RIR database for the space.65 of 673
Route object: RIR187.86.19.0/24Route object only in ALTDB. Add it in the RIR database for the space.65 of 673

Route objects not announced

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