bgpreport

Network · data from 2026-11-12

AS274156 AS274156 - TELDRA S.A.C.

Registry name: AS274156 - TELDRA S.A.C., PE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274156, 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.252.218.0/24 Invalid: origin Other origin only 2 0%low visibility 2
177.221.146.0/24 No ROA Other IRR onlyRADB 673 100% 67
38.252.215.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.252.212.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
132.255.239.0/24 Valid Other origin only 672 100% 67
132.255.236.0/24 Valid Other IRR onlyRADB 673 100% 67
132.255.237.0/24 Valid Other IRR onlyRADB 672 100% 67
132.255.238.0/24 Valid Other IRR onlyRADB 672 100% 67
2803:99d0::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS274156 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin1
  • ROA: none3
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin38.252.218.0/24ROAs covering it name AS273000, not AS274156. If AS274156 should announce it, add a ROA for AS274156.2 of 673
Route object: none38.252.218.0/24Route objects for it name AS273000. Add a route object with origin AS274156 in the RIR database for the space.2 of 673
ROA: none177.221.146.0/24No ROA covers it. Add a ROA for AS274156, maxLength 24.673 of 673
Route object: RIR177.221.146.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.252.215.0/24No ROA covers it. Add a ROA for AS274156, maxLength 24.672 of 673
Route object: RIR38.252.215.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.252.212.0/24No ROA covers it. Add a ROA for AS274156, maxLength 24.2 of 673
Route object: RIR38.252.212.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none132.255.239.0/24Route objects for it name AS52439. Add a route object with origin AS274156 in the RIR database for the space.672 of 673
Route object: RIR132.255.236.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR132.255.237.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

132.255.236.0/23RADBValid

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.