bgpreport

Network · data from 2026-11-12

AS36136 ALARMNET - ALARMNET

Registry name: ALARMNET - ALARMNET, US · not in PeeringDB

8IPv4 routes 87.5% 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
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS36136, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36136, 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.
12.149.218.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.140.154.0/23 Valid Other IRR onlyRADB 673 100% 67
204.141.56.0/22 Valid Other IRR onlyRADB 673 100% 67
204.141.56.0/23 Valid Other IRR onlyNTTCOM 673 100% 67
204.141.58.0/23 Valid Other IRR onlyNTTCOM 673 100% 67
131.201.236.0/24 Valid RIR databaseARIN, RADB 673 100% 67
131.201.237.0/24 Valid RIR databaseARIN 673 100% 67
198.140.155.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS36136 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none12.149.218.0/24No ROA covers it. Add a ROA for AS36136, maxLength 24.673 of 673
Route object: RIR12.149.218.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.140.154.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.141.56.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.141.56.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR204.141.58.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

12.188.18.0/24ALTDB, RADBNo ROA
131.201.64.0/23RADBNo ROA
199.62.71.0/24ALTDBNo ROA
199.62.84.0/24RADBNo ROA
204.141.56.0/24RADBValid
204.141.57.0/24RADBValid
204.141.58.0/24RADBValid
204.141.59.0/24RADBValid

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.