bgpreport

Network · data from 2026-11-12

AS262313 Internet Pinheirense Ltda - ME

Registry name: AS262313 - Internet Pinheirense Ltda - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262313, 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:8564:f000::/40 Valid Nonecovered by 2804:8564::/32 636 100% 67
177.105.224.0/20 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
177.105.224.0/21 Valid Other IRR onlyALTDB, RADB 672 100% 66
177.105.224.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.105.224.0/23 Valid Other IRR onlyALTDB 672 100% 66
177.105.226.0/23 Valid Other IRR onlyALTDB 672 100% 66
177.105.228.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.105.232.0/21 Valid Other IRR onlyALTDB, RADB 672 100% 66
177.105.236.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.105.238.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
177.105.230.0/23 Valid Other IRR onlyALTDB 670 100% 67
177.105.232.0/23 Valid Other IRR onlyALTDB 670 100% 67
177.105.236.0/23 Valid Other IRR onlyALTDB, RADB 670 100% 67
177.105.226.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 66
177.105.231.0/24 Valid Other IRR onlyALTDB, RADB 668 99% 67
2804:8564::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
177.105.227.0/24 Valid Other IRR onlyALTDB 203 30% 54
177.105.232.0/24 Valid Other IRR onlyALTDB, RADB 203 30% 54
177.105.233.0/24 Valid Other IRR onlyALTDB, RADB 203 30% 54
177.105.236.0/24 Valid Other IRR onlyALTDB, RADB 203 30% 54
177.105.237.0/24 Valid Other IRR onlyALTDB, RADB 203 30% 54
177.105.239.0/24 Valid Other IRR onlyALTDB, RADB 203 30% 54
177.105.224.0/24 Valid Other IRR onlyALTDB 202 30% 54
177.105.228.0/24 Valid Other IRR onlyALTDB, RADB 202 30% 54
177.105.229.0/24 Valid Other IRR onlyALTDB, RADB 202 30% 54
177.105.238.0/24 Valid Other IRR onlyALTDB, RADB 202 30% 54
177.105.225.0/24 Valid Other IRR onlyALTDB, RADB 201 30% 54
177.105.230.0/24 Valid Other IRR onlyALTDB, RADB 201 30% 54
177.105.228.0/23 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 3
177.105.232.0/22 Valid Other IRR onlyALTDB 2 0%low visibility 3
177.105.234.0/23 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 3
177.105.235.0/24 Valid Other IRR onlyALTDB, RADB 0 0%low visibility 1

AS-SET

AS262313's PeeringDB record names no AS-SET.

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 34 are in fix.csv.

  • Route object: none1
  • Route object: RIR31
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:8564:f000::/40No route object for it. A route object for 2804:8564::/32 with origin AS262313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262313 in the RIR database for the space.636 of 636
Route object: RIR177.105.224.0/20Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.224.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.224.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.224.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.226.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.228.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.232.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.236.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.238.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.230.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.105.232.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.105.236.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.105.226.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.105.231.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:8564::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR177.105.227.0/24Route object only in ALTDB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.232.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.233.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.236.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.237.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.239.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.105.224.0/24Route object only in ALTDB. Add it in the RIR database for the space.202 of 673
Route object: RIR177.105.228.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR177.105.229.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR177.105.238.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR177.105.225.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR177.105.230.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR177.105.228.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.105.232.0/22Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.105.234.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.105.235.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

177.105.234.0/24ALTDB, RADBValid
2804:6820::/32ALTDBNo ROA

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.