bgpreport

Network · data from 2026-11-12

AS271770 PINGUIM TELECOM E TECNOLOGIA

Registry name: AS271770 - PINGUIM TELECOM E TECNOLOGIA EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271770, 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.
38.7.110.0/23 No ROA Other IRR onlyRADB 671 100% 67
38.7.110.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.7.111.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:80bc::/32 No ROA Other IRR onlyALTDB, RADB, TC 636 100% 67
2804:80bc::/33 No ROA Other IRR onlyRADB, TC 636 100% 67
2804:80bc:8000::/33 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS271770: AS271770:AS-ANNOUNCEMENTS. 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 (AS271770 isn't in the set, or no route object for AS271770 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 objectsAS271770 in itNot covered
AS271770:AS-ANNOUNCEMENTS TC 2216 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 12 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none38.7.110.0/23No ROA covers it. Add a ROA for AS271770, maxLength 23.671 of 673
Route object: RIR38.7.110.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.7.110.0/24No ROA covers it. Add a ROA for AS271770, maxLength 24.670 of 673
Route object: RIR38.7.110.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.7.111.0/24No ROA covers it. Add a ROA for AS271770, maxLength 24.670 of 673
Route object: RIR38.7.111.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:80bc::/32No ROA covers it. Add a ROA for AS271770, maxLength 32.636 of 636
Route object: RIR2804:80bc::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:80bc::/33No ROA covers it. Add a ROA for AS271770, maxLength 33.636 of 636
Route object: RIR2804:80bc::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:80bc:8000::/33No ROA covers it. Add a ROA for AS271770, maxLength 33.636 of 636
Route object: RIR2804:80bc:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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