bgpreport

Network · data from 2026-11-12

AS4613 MOS-NP - Mercantile Office Systems

Registry name: MOS-NP - Mercantile Office Systems, NP · not in PeeringDB

31IPv4 routes 96.8% 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
1Low visibility seen by under 10% of full-table peers
25Route objects not announced registered with origin AS4613, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4613, 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.
27.111.16.0/20 No ROA Other IRR onlyRADB 670 100% 66
117.121.224.0/20 Valid RIR databaseAPNIC, RADB 671 100% 66
117.121.225.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.226.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.227.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.228.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.229.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.231.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.232.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.233.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.234.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.235.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.236.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.237.0/24 Valid RIR databaseAPNIC 671 100% 66
117.121.239.0/24 Valid RIR databaseAPNIC 671 100% 66
27.111.17.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.18.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.19.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.20.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.21.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.24.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.25.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.26.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.27.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.28.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.29.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.30.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.31.0/24 Valid RIR databaseAPNIC 669 99% 66
27.111.23.0/24 Valid RIR databaseAPNIC 667 99% 66
117.121.230.0/24 Valid RIR databaseAPNIC 634 94% 65
27.111.22.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none27.111.16.0/20No ROA covers it. Add a ROA for AS4613, maxLength 20.670 of 673
Route object: RIR27.111.16.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

27.111.16.0/22APNICValid
27.111.16.0/23APNICValid
27.111.16.0/24APNICValid
27.111.18.0/23APNICValid
27.111.24.0/22APNICValid
27.111.26.0/23APNICValid
27.111.28.0/23APNICValid
27.111.30.0/23APNICValid
117.121.224.0/21APNICValid
117.121.224.0/22APNICValid
117.121.224.0/23APNICValid
117.121.224.0/24APNICValid
117.121.226.0/23APNICValid
117.121.228.0/22APNICValid
117.121.228.0/23APNICValid
117.121.230.0/23APNICValid
117.121.232.0/21APNICValid
117.121.232.0/22APNICValid
117.121.232.0/23APNICValid
117.121.234.0/23APNICValid
117.121.236.0/22APNICValid
117.121.236.0/23APNICValid
117.121.238.0/23APNICValid
117.121.238.0/24APNICValid
202.52.250.0/24RADBNo 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.