bgpreport

Network · data from 2026-11-12

AS271875 AS271875 - MARATEL CA

Registry name: AS271875 - MARATEL CA, VE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271875, 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.
45.195.25.0/24 Invalid: origin Other origin only 2 0%low visibility 2
13.143.240.0/24 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin45.195.25.0/24ROAs covering it name AS17561, not AS271875. If AS271875 should announce it, add a ROA for AS271875.2 of 673
Route object: none45.195.25.0/24Route objects for it name AS17561, AS211871. Add a route object with origin AS271875 in the RIR database for the space.2 of 673

Route objects not announced

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

154.95.53.0/24AFRINICInvalid: origin
201.218.190.0/23RADBNo 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.