bgpreport

Network · data from 2026-11-12

AS272739 Lider Fibra

Registry name: AS272739 - Lider Fibra, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272739, 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.156.70.0/24 Invalid: origin Other origin only 5 1%low visibility 3
38.156.71.0/24 No ROA Other IRR onlyRADB 255 38% 54
2804:87e8::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:87e8::/34 Valid Other IRR onlyTC 352 55% 65
2804:87e8:4000::/34 Valid Other IRR onlyTC 352 55% 65
2804:87e8:8000::/34 Valid Other IRR onlyTC 352 55% 65
2804:87e8:c000::/34 Valid Other IRR onlyTC 352 55% 65

AS-SET

PeeringDB's irr_as_set for AS272739: AS272739:AS-SET. 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 (AS272739 isn't in the set, or no route object for AS272739 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 objectsAS272739 in itNot covered
AS272739:AS-SET In no IRR database read today.

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR6
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: origin38.156.70.0/24ROAs covering it name AS274226, not AS272739. If AS272739 should announce it, add a ROA for AS272739.5 of 673
Route object: none38.156.70.0/24Route objects for it name AS274226. Add a route object with origin AS272739 in the RIR database for the space.5 of 673
ROA: none38.156.71.0/24No ROA covers it. Add a ROA for AS272739, maxLength 24.255 of 673
Route object: RIR38.156.71.0/24Route object only in RADB. Add it in the RIR database for the space.255 of 673
Route object: RIR2804:87e8::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87e8::/34Route object only in TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:87e8:4000::/34Route object only in TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:87e8:8000::/34Route object only in TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:87e8:c000::/34Route object only in TC. Add it in the RIR database for the space.352 of 636
AS-SET: not foundAS272739:AS-SETPeeringDB names AS272739:AS-SET; no IRR database read has it.

Route objects not announced

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