bgpreport

Network · data from 2026-11-12

AS271445 PORTO NET TELECOMUNICAÇÕES

Registry name: AS271445 - PORTO NET TELECOMUNICACOES LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271445, 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.49.84.0/23 No ROA Nonecovered by 179.49.84.0/22 670 100% 67
179.49.85.0/24 No ROA Nonecovered by 179.49.84.0/22 670 100% 67
179.49.86.0/23 No ROA Nonecovered by 179.49.84.0/22 669 99% 67
179.49.86.0/24 No ROA Nonecovered by 179.49.84.0/22 669 99% 67
179.49.87.0/24 No ROA Nonecovered by 179.49.84.0/22 669 99% 67
2804:7ba4::/36 No ROA Nonecovered by 2804:7ba4::/32 634 100% 67
179.49.84.0/24 No ROA Other IRR onlyRADB 673 100% 67
2804:7ba4::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS271445: TC::AS271445. 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 (AS271445 isn't in the set, or no route object for AS271445 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 objectsAS271445 in itNot covered
TC::AS271445 A single AS number, not a set: AS271445 (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 17 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none179.49.84.0/23No ROA covers it. Add a ROA for AS271445, maxLength 23.670 of 673
Route object: none179.49.84.0/23No route object for it. A route object for 179.49.84.0/22 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.670 of 673
ROA: none179.49.85.0/24No ROA covers it. Add a ROA for AS271445, maxLength 24.670 of 673
Route object: none179.49.85.0/24No route object for it. A route object for 179.49.84.0/22 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.670 of 673
ROA: none179.49.86.0/23No ROA covers it. Add a ROA for AS271445, maxLength 23.669 of 673
Route object: none179.49.86.0/23No route object for it. A route object for 179.49.84.0/22 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.669 of 673
ROA: none179.49.86.0/24No ROA covers it. Add a ROA for AS271445, maxLength 24.669 of 673
Route object: none179.49.86.0/24No route object for it. A route object for 179.49.84.0/22 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.669 of 673
ROA: none179.49.87.0/24No ROA covers it. Add a ROA for AS271445, maxLength 24.669 of 673
Route object: none179.49.87.0/24No route object for it. A route object for 179.49.84.0/22 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.669 of 673
ROA: none2804:7ba4::/36No ROA covers it. Add a ROA for AS271445, maxLength 36.634 of 636
Route object: none2804:7ba4::/36No route object for it. A route object for 2804:7ba4::/32 with origin AS271445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271445 in the RIR database for the space.634 of 636
ROA: none179.49.84.0/24No ROA covers it. Add a ROA for AS271445, maxLength 24.673 of 673
Route object: RIR179.49.84.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2804:7ba4::/32No ROA covers it. Add a ROA for AS271445, maxLength 32.634 of 636
Route object: RIR2804:7ba4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

179.49.84.0/22RADBNo 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.