bgpreport

Network · data from 2026-11-12

AS214656 MARAPHON-AS Maraphon JSC

Registry name: MARAPHON-AS Maraphon JSC, RU · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS214656, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214656, 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.
193.228.146.0/32 No ROA Nonecovered by 193.228.146.0/24 5 1%low visibility 8
193.228.146.0/24 No ROA RIR databaseRIPE 673 100% 66
212.74.252.0/23 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS214656 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: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.228.146.0/32No ROA covers it. Add a ROA for AS214656, maxLength 32.5 of 673
Route object: none193.228.146.0/32No route object for it. A route object for 193.228.146.0/24 with origin AS214656 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214656 in the RIR database for the space.5 of 673
ROA: none193.228.146.0/24No ROA covers it. Add a ROA for AS214656, maxLength 24.673 of 673
ROA: none212.74.252.0/23No ROA covers it. Add a ROA for AS214656, maxLength 23.673 of 673

Route objects not announced

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