bgpreport

Network · data from 2026-11-12

AS272213 POUPANET TELECOM

Registry name: AS272213 - POUPA NET TELECOM LTDA, BR · PeeringDB

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

Announced routes

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

138.117.226.0/24 No ROA Other IRR onlyTC 672 100% 67
138.117.227.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
2804:83b4::/32 No ROA Other IRR onlyALTDB, RADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS272213: AS-POUPANET. 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 (AS272213 isn't in the set, or no route object for AS272213 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 objectsAS272213 in itNot covered
AS-POUPANET ALTDB 3128 No 3

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.

  • ROA: none3
  • Route object: RIR3
  • AS-SET: own ASN1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none138.117.226.0/24No ROA covers it. Add a ROA for AS272213, maxLength 24.672 of 673
Route object: RIR138.117.226.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none138.117.227.0/24No ROA covers it. Add a ROA for AS272213, maxLength 24.672 of 673
Route object: RIR138.117.227.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:83b4::/32No ROA covers it. Add a ROA for AS272213, maxLength 32.632 of 636
Route object: RIR2804:83b4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636
AS-SET: own ASNAS-POUPANETAS272213 isn't in AS-POUPANET (ALTDB) once expanded. Add AS272213 to it.

Route objects not announced

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

38.50.168.0/23ALTDBNo ROA
38.50.168.0/24ALTDBNo ROA
38.50.169.0/24ALTDBNo ROA
38.50.170.0/23ALTDBNo ROA
38.50.170.0/24ALTDBNo ROA
38.50.171.0/24ALTDBNo ROA
138.117.226.0/23RADB, TCNo 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.