bgpreport

Network · data from 2026-11-12

AS51026 MobinhostInfrastructure

Registry name: MobinhostInfrastructure Dade Pardazi Mobinhost Co LTD, IR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51026, 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.

5.56.133.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
62.220.125.0/24 Valid RIR databaseRIPE 671 100% 67
185.53.141.0/24 Valid RIR databaseRIPE 671 100% 66
185.53.142.0/24 Valid RIR databaseRIPE 671 100% 67
185.53.143.0/24 Valid RIR databaseRIPE 671 100% 67
87.107.153.0/24 Valid RIR databaseRIPE 670 100% 66
87.236.209.0/24 Valid RIR databaseRIPE 670 100% 66
62.220.124.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.3.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.6.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.7.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.8.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.109.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
87.107.111.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.3.124.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS51026's PeeringDB record names no 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 48 are in fix.csv.

  • ROA: none1
  • Route object: not announced47
ChangePrefix or setDetailFull-table peers
ROA: none5.56.133.0/24No ROA covers it. Add a ROA for AS51026, maxLength 24.2 of 673

Route objects not announced

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

5.56.132.0/24RIPEValid
45.129.36.0/24RIPEValid
45.129.37.0/24RIPEValid
45.129.38.0/24RIPEValid
45.129.39.0/24RIPEValid
62.220.122.0/24RIPEValid
62.220.123.0/24RIPEValid
62.220.126.0/24RIPEValid
62.220.127.0/24RIPEValid
79.143.84.0/24RIPEValid
80.75.213.0/24RIPEValid
81.12.24.0/24RIPEValid
81.12.25.0/24RIPEValid
81.12.26.0/24RIPEValid
81.12.27.0/24RIPEValid
81.12.30.0/24RIPEValid
81.12.31.0/24RIPEValid
85.8.230.0/24RIPEValid
87.107.0.0/24RIPEValid
87.107.1.0/24RIPEValid
87.107.2.0/24RIPEValid
87.107.4.0/24RIPEValid
87.107.5.0/24RIPEValid
87.107.6.0/23RIPEValid
87.107.8.0/23RIPEValid
87.107.9.0/24RIPEValid
87.107.108.0/23RIPEValid
87.107.108.0/24RIPEValid
87.107.110.0/24RIPEValid
87.107.128.0/22RIPEValid
87.107.128.0/24RIPEValid
87.107.129.0/24RIPEValid
87.107.130.0/24RIPEValid
87.107.131.0/24RIPEValid
87.107.144.0/24RIPEValid
87.107.152.0/24RIPEValid
87.107.160.0/24RIPEValid
87.107.161.0/24RIPEValid
87.107.166.0/24RIPEValid
87.107.167.0/24RIPEValid
87.107.174.0/24RIPEValid
87.107.175.0/24RIPEValid
87.236.212.0/24RIPEValid
185.126.202.0/24RIPEValid
185.126.203.0/24RIPEValid
194.156.77.0/24RIPEValid
2a0d:9680::/48RIPEValid

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.