bgpreport

Network · data from 2026-11-12

AS55083 NUMEREX - Numerex Corp

Registry name: NUMEREX - Numerex Corp, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55083, 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.
192.119.176.0/20 No ROA Other IRR onlyRADB 673 100% 67
192.119.176.0/21 No ROA Other IRR onlyRADB 673 100% 67
192.119.184.0/21 No ROA Other IRR onlyRADB 673 100% 67
199.91.164.0/22 No ROA Other IRR onlyRADB 673 100% 67
2606:e480::/32 No ROA Other IRR onlyRADB 636 100% 67
2606:e480:100::/40 No ROA Other IRR onlyRADB 636 100% 67
2606:e480:300::/40 No ROA Other IRR onlyRADB 636 100% 67
184.60.223.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS55083 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 23 are in fix.csv.

  • ROA: none7
  • Route object: RIR8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none192.119.176.0/20No ROA covers it. Add a ROA for AS55083, maxLength 20.673 of 673
Route object: RIR192.119.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.119.176.0/21No ROA covers it. Add a ROA for AS55083, maxLength 21.673 of 673
Route object: RIR192.119.176.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.119.184.0/21No ROA covers it. Add a ROA for AS55083, maxLength 21.673 of 673
Route object: RIR192.119.184.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.91.164.0/22No ROA covers it. Add a ROA for AS55083, maxLength 22.673 of 673
Route object: RIR199.91.164.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2606:e480::/32No ROA covers it. Add a ROA for AS55083, maxLength 32.636 of 636
Route object: RIR2606:e480::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2606:e480:100::/40No ROA covers it. Add a ROA for AS55083, maxLength 40.636 of 636
Route object: RIR2606:e480:100::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2606:e480:300::/40No ROA covers it. Add a ROA for AS55083, maxLength 40.636 of 636
Route object: RIR2606:e480:300::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR184.60.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

12.107.219.0/24RADBNo ROA
12.129.114.0/24RADBNo ROA
12.130.210.0/23RADBNo ROA
12.155.222.0/23RADBNo ROA
192.119.187.0/24RADBNo ROA
199.91.164.0/24RADBNo ROA
2606:e480:4000::/36RADBNo ROA
2606:e480:7000::/36RADBNo 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.