bgpreport

Network · data from 2026-11-12

AS271255 Peer Telecom LTDA

Registry name: AS271255 - PEER 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
5Route objects not announced registered with origin AS271255, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271255, 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.99.156.0/22 No ROA Other IRR onlyRADB, TC 667 99% 67
138.99.157.0/24 No ROA Other IRR onlyTC 667 99% 67
2804:78a0::/32 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS271255: AS271255:AS-ALL. 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 (AS271255 isn't in the set, or no route object for AS271255 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 objectsAS271255 in itNot covered
AS271255:AS-ALL TClists itself further down3 member sets in no database: AS-RMS, AS-SNT-28604, AS264461:AS-ANNOUNCEMENTS 5833817 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 14 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • AS-SET: missing member3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none138.99.156.0/22No ROA covers it. Add a ROA for AS271255, maxLength 22.667 of 673
Route object: RIR138.99.156.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none138.99.157.0/24No ROA covers it. Add a ROA for AS271255, maxLength 24.667 of 673
Route object: RIR138.99.157.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:78a0::/32No ROA covers it. Add a ROA for AS271255, maxLength 32.631 of 636
Route object: RIR2804:78a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
AS-SET: missing memberAS271255:AS-ALLAS271255:AS-ALL (TC) lists AS-RMS; no IRR database read has it.
AS-SET: missing memberAS271255:AS-ALLAS271255:AS-ALL (TC) lists AS-SNT-28604; no IRR database read has it.
AS-SET: missing memberAS271255:AS-ALLAS271255:AS-ALL (TC) lists AS264461:AS-ANNOUNCEMENTS; no IRR database read has it.

Route objects not announced

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

138.99.156.0/23TCNo ROA
138.99.156.0/24TCNo ROA
138.99.158.0/23TCNo ROA
138.99.158.0/24TCNo ROA
138.99.159.0/24TCNo 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.