bgpreport

Network · data from 2026-11-12

AS2015 MSEN-SYSTEM

Registry name: MSEN-SYSTEM - Msen, Inc., US · PeeringDB

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

Announced routes

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

198.11.56.0/24 No ROA Other IRR onlyALTDB 671 100% 67
148.59.14.0/24 No ROA Other IRR onlyALTDB 670 100% 68
148.59.19.0/24 No ROA Other IRR onlyALTDB 670 100% 68
148.59.21.0/24 No ROA Other IRR onlyALTDB 670 100% 68
148.59.50.0/24 No ROA Other IRR onlyALTDB 670 100% 68
148.59.80.0/21 No ROA Other IRR onlyALTDB 670 100% 68
198.11.32.0/19 No ROA Other IRR onlyALTDB 670 100% 68
198.202.235.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 68

AS-SET

AS2015'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 31 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none198.11.56.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.671 of 673
Route object: RIR198.11.56.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none148.59.14.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.670 of 673
Route object: RIR148.59.14.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none148.59.19.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.670 of 673
Route object: RIR148.59.19.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none148.59.21.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.670 of 673
Route object: RIR148.59.21.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none148.59.50.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.670 of 673
Route object: RIR148.59.50.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none148.59.80.0/21No ROA covers it. Add a ROA for AS2015, maxLength 21.670 of 673
Route object: RIR148.59.80.0/21Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none198.11.32.0/19No ROA covers it. Add a ROA for AS2015, maxLength 19.670 of 673
Route object: RIR198.11.32.0/19Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none198.202.235.0/24No ROA covers it. Add a ROA for AS2015, maxLength 24.670 of 673
Route object: RIR198.202.235.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

139.171.0.0/16ALTDBNo ROA
148.59.48.0/21ALTDBNo ROA
192.86.2.0/24ALTDBNo ROA
192.169.64.0/23ALTDBNo ROA
192.206.182.0/24ALTDBNo ROA
198.11.32.0/24ALTDBNo ROA
198.11.56.0/22RADBNo ROA
198.51.241.0/24ALTDBNo ROA
198.99.87.0/24ALTDBNo ROA
198.99.113.0/24ALTDBNo ROA
198.153.219.0/24ALTDBNo ROA
198.187.156.0/24ALTDBNo ROA
199.201.160.0/24ALTDBNo ROA
208.211.112.0/20ALTDBNo ROA
208.212.120.0/21ALTDBNo 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.