bgpreport

Network · data from 2026-11-12

AS21581 M5 Computer Security / M5Hosting

Registry name: M5HOSTING - M5 Computer Security, US · PeeringDB

23IPv4 routes 82.6% RPKI valid · 56.5% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
3No ROA 10 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS21581, seen from no peer

Announced routes

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

108.161.157.0/24 Invalid: maxLength Nonecovered by 108.161.144.0/20 37 5%low visibility 25
38.96.14.0/24 No ROA None 669 99% 67
66.238.186.0/24 No ROA Other origin only 668 99% 69
98.158.160.0/20 No ROA Other origin only 668 99% 69
108.161.145.0/24 Valid Nonecovered by 108.161.144.0/20 670 100% 68
108.161.148.0/24 Valid Nonecovered by 108.161.144.0/20 670 100% 68
108.161.156.0/23 Valid Nonecovered by 108.161.144.0/20 670 100% 69
108.161.144.0/24 Valid Nonecovered by 108.161.144.0/20 669 99% 68
108.161.146.0/24 Valid Nonecovered by 108.161.144.0/20 669 99% 68
108.161.151.0/24 Valid Nonecovered by 108.161.144.0/20 669 99% 68
108.161.144.0/20 Valid Other IRR onlyRADB 2 0%low visibility 2
108.161.156.0/24 Valid RIR databaseARIN 670 100% 68
209.216.206.0/24 Valid RIR databaseARIN 670 100% 68
206.71.169.0/24 Valid RIR databaseARIN 669 99% 68
206.71.179.0/24 Valid RIR databaseARIN 669 99% 68
206.71.190.0/24 Valid RIR databaseARIN 669 99% 68
206.251.244.0/24 Valid RIR databaseARIN 669 99% 68
206.251.255.0/24 Valid RIR databaseARIN 669 99% 68
207.158.15.0/24 Valid RIR databaseARIN 669 99% 68
207.158.30.0/24 Valid RIR databaseARIN 669 99% 68
207.158.37.0/24 Valid RIR databaseARIN 669 99% 68
209.216.230.0/24 Valid RIR databaseARIN 669 99% 68
207.158.52.0/24 Valid RIR databaseARIN 666 99% 68
2606:7100::/32 Valid RIR databaseARIN 635 100% 70
2606:7100:1cab::/48 Valid RIR databaseARIN 635 100% 70
2606:7100:3100::/44 Valid RIR databaseARIN 634 100% 70
2606:7100:3200::/44 Valid RIR databaseARIN 605 95% 67

AS-SET

AS21581'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 16 are in fix.csv.

  • ROA: maxLength1
  • ROA: none3
  • Route object: none10
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength108.161.157.0/24ROA 108.161.144.0/20 AS21581 has maxLength 20; ROA 108.161.156.0/23 AS21581 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 108.161.157.0/24.37 of 673
Route object: none108.161.157.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.37 of 673
ROA: none38.96.14.0/24No ROA covers it. Add a ROA for AS21581, maxLength 24.669 of 673
Route object: none38.96.14.0/24No route object for it. Add a route object with origin AS21581 in the RIR database for the space.669 of 673
ROA: none66.238.186.0/24No ROA covers it. Add a ROA for AS21581, maxLength 24.668 of 673
Route object: none66.238.186.0/24Route objects for it name AS29819. Add a route object with origin AS21581 in the RIR database for the space.668 of 673
ROA: none98.158.160.0/20No ROA covers it. Add a ROA for AS21581, maxLength 20.668 of 673
Route object: none98.158.160.0/20Route objects for it name AS29819. Add a route object with origin AS21581 in the RIR database for the space.668 of 673
Route object: none108.161.145.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.670 of 673
Route object: none108.161.148.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.670 of 673
Route object: none108.161.156.0/23No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.670 of 673
Route object: none108.161.144.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.669 of 673
Route object: none108.161.146.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.669 of 673
Route object: none108.161.151.0/24No route object for it. A route object for 108.161.144.0/20 with origin AS21581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21581 in the RIR database for the space.669 of 673
Route object: RIR108.161.144.0/20Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2606:7100:3000::/44ARINValid

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.