bgpreport

Network · data from 2026-11-12

AS213915 HOSTES-AS HOSTES LTD

Registry name: HOSTES-AS HOSTES LTD, GB · not in PeeringDB

88IPv4 routes 81.8% RPKI valid · 83.0% with a route object
0IPv6 routes
6RPKI invalid 6 origin · 0 maxLength
10No ROA 15 with no route object for this origin
16Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS213915, seen from no peer

Announced routes

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

45.151.71.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.183.222.0/24 Invalid: origin None 2 0%low visibility 2
31.59.223.0/24 Invalid: origin Other origin only 1 0%low visibility 1
94.183.223.0/24 Invalid: origin Other origin only 1 0%low visibility 1
151.246.128.0/24 Invalid: origin None 1 0%low visibility 1
217.60.74.0/24 Invalid: origin Other origin only 1 0%low visibility 1
151.247.168.0/24 No ROA None 3 0%low visibility 3
217.60.17.0/24 No ROA None 3 0%low visibility 3
151.242.160.0/24 No ROA None 2 0%low visibility 2
151.242.161.0/24 No ROA None 2 0%low visibility 2
151.242.162.0/24 No ROA None 2 0%low visibility 2
151.242.163.0/24 No ROA None 1 0%low visibility 1
217.60.16.0/24 No ROA None 1 0%low visibility 1
217.60.75.0/24 No ROA None 1 0%low visibility 1
217.60.207.0/24 No ROA None 0 0%low visibility 1
31.58.184.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
91.214.78.0/24 Valid RIR databaseRIPE 673 100% 66
94.183.229.0/24 Valid RIR databaseRIPE 673 100% 67
31.56.55.0/24 Valid RIR databaseRIPE 672 100% 66
31.56.214.0/24 Valid RIR databaseRIPE 672 100% 66
31.57.22.0/24 Valid RIR databaseRIPE 672 100% 66
31.57.23.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.92.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.93.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.116.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.118.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.119.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.177.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.240.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.252.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.253.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.254.0/24 Valid RIR databaseRIPE 672 100% 66
31.58.255.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.36.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.127.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.142.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.149.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.208.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.221.0/24 Valid RIR databaseRIPE 672 100% 66
31.77.45.0/24 Valid RIR databaseRIPE 672 100% 66
79.175.88.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
94.183.152.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.161.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.200.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.201.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.202.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.204.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.205.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.217.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.219.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.221.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.228.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.242.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.243.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.246.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.253.0/24 Valid RIR databaseRIPE 672 100% 66
94.183.255.0/24 Valid RIR databaseRIPE 672 100% 66
151.245.174.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
187.55.164.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.13.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.23.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.24.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.64.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.68.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.94.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.95.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.176.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.181.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.205.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.206.0/24 Valid RIR databaseRIPE 672 100% 66
217.60.251.0/24 Valid RIR databaseRIPE 672 100% 66
31.56.188.0/24 Valid RIR databaseRIPE 671 100% 68
31.58.117.0/24 Valid RIR databaseRIPE 671 100% 68
31.58.176.0/24 Valid RIR databaseRIPE 671 100% 68
31.58.180.0/24 Valid RIR databaseRIPE 671 100% 66
31.58.213.0/24 Valid RIR databaseRIPE 671 100% 66
31.58.234.0/24 Valid RIR databaseRIPE 671 100% 66
31.58.235.0/24 Valid RIR databaseRIPE 671 100% 68
31.59.124.0/24 Valid RIR databaseRIPE 671 100% 68
31.59.125.0/24 Valid RIR databaseRIPE 671 100% 68
37.235.192.0/24 Valid RIR databaseRIPE 671 100% 68
94.183.157.0/24 Valid RIR databaseRIPE 671 100% 68
94.183.230.0/24 Valid RIR databaseRIPE 671 100% 66
94.183.241.0/24 Valid RIR databaseRIPE 671 100% 68
217.60.31.0/24 Valid RIR databaseRIPE 671 100% 66
217.60.65.0/24 Valid RIR databaseRIPE 671 100% 68
31.56.182.0/24 Valid RIR databaseRIPE 666 99% 66
77.221.146.0/24 Valid RIR databaseRIPE 655 97% 66

AS-SET

AS213915 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 34 are in fix.csv.

  • ROA: origin6
  • ROA: none10
  • Route object: none15
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin45.151.71.0/24ROAs covering it name AS219202, not AS213915. If AS213915 should announce it, add a ROA for AS213915.2 of 673
Route object: none45.151.71.0/24Route objects for it name AS210079. Add a route object with origin AS213915 in the RIR database for the space.2 of 673
ROA: origin94.183.222.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213915 should announce it, add a ROA for AS213915.2 of 673
Route object: none94.183.222.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.2 of 673
ROA: origin31.59.223.0/24ROAs covering it name AS218757, not AS213915. If AS213915 should announce it, add a ROA for AS213915.1 of 673
Route object: none31.59.223.0/24Route objects for it name AS218757. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: origin94.183.223.0/24ROAs covering it name AS212056, not AS213915. If AS213915 should announce it, add a ROA for AS213915.1 of 673
Route object: none94.183.223.0/24Route objects for it name AS212056. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: origin151.246.128.0/24ROAs covering it name AS834, AS211484, not AS213915. If AS213915 should announce it, add a ROA for AS213915.1 of 673
Route object: none151.246.128.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: origin217.60.74.0/24ROAs covering it name AS24940, not AS213915. If AS213915 should announce it, add a ROA for AS213915.1 of 673
Route object: none217.60.74.0/24Route objects for it name AS24940. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: none151.247.168.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.3 of 673
Route object: none151.247.168.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.3 of 673
ROA: none217.60.17.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.3 of 673
Route object: none217.60.17.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.3 of 673
ROA: none151.242.160.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.2 of 673
Route object: none151.242.160.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.2 of 673
ROA: none151.242.161.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.2 of 673
Route object: none151.242.161.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.2 of 673
ROA: none151.242.162.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.2 of 673
Route object: none151.242.162.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.2 of 673
ROA: none151.242.163.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.1 of 673
Route object: none151.242.163.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: none217.60.16.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.1 of 673
Route object: none217.60.16.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: none217.60.75.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.1 of 673
Route object: none217.60.75.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.1 of 673
ROA: none217.60.207.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.0 of 673
Route object: none217.60.207.0/24No route object for it. Add a route object with origin AS213915 in the RIR database for the space.0 of 673
ROA: none31.58.184.0/24No ROA covers it. Add a ROA for AS213915, maxLength 24.2 of 673

Route objects not announced

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

31.58.185.0/24RIPENo ROA
31.59.116.0/24RIPEValid
187.54.15.0/24RIPEValid

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.