bgpreport

Network · data from 2026-11-12

AS198584 PIO-Hosting PIO-Hosting GmbH

Registry name: PIO-Hosting PIO-Hosting GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198584, 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.87.248.0/24 Invalid: origin Other origin only 2 0%low visibility 2
64.89.162.0/24 Invalid: origin Other origin only 2 0%low visibility 2
78.154.116.0/24 Invalid: origin Other origin only 1 0%low visibility 1
151.242.148.0/24 Invalid: origin Other origin only 1 0%low visibility 1
213.214.108.0/24 Invalid: origin Other origin only 1 0%low visibility 1
217.60.27.0/24 Invalid: origin Other origin only 1 0%low visibility 1
181.214.121.0/24 Invalid: origin Other IRR onlyRADB 171 25% 45
85.133.216.0/24 Invalid: origin RIR databaseRIPE 2 0%low visibility 2
176.65.128.0/24 No ROA RIR databaseRIPE 673 100% 66
176.65.131.0/24 No ROA RIR databaseRIPE 673 100% 66
176.65.135.0/24 No ROA RIR databaseRIPE 673 100% 66
176.65.136.0/24 No ROA RIR databaseRIPE 673 100% 66
40.27.130.0/24 Valid RIR databaseARIN, RADB 673 100% 66
40.27.131.0/24 Valid RIR databaseARIN, RADB 673 100% 66
40.27.224.0/24 Valid RIR databaseARIN, RADB 673 100% 66
64.204.70.0/24 Valid RIR databaseARIN, RADB 673 100% 66
68.164.70.0/24 Valid RIR databaseARIN, RADB 673 100% 66
78.154.122.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
83.245.64.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
91.245.220.0/24 Valid RIR databaseRIPE 673 100% 66
92.246.87.0/24 Valid RIR databaseRIPE 673 100% 66
94.118.71.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
94.118.90.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
103.161.34.0/23 Valid RIR databaseAPNIC 673 100% 66
143.14.65.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
145.79.131.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.79.0.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
151.245.219.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
162.244.59.0/24 Valid RIR databaseARIN, RADB 673 100% 66
162.244.60.0/24 Valid RIR databaseARIN, RADB 673 100% 66
162.244.61.0/24 Valid RIR databaseARIN, RADB 673 100% 66
162.244.62.0/24 Valid RIR databaseARIN, RADB 673 100% 66
192.156.217.0/24 Valid RIR databaseRIPE 673 100% 66
194.120.171.0/24 Valid RIR databaseRIPE 673 100% 66
194.120.230.0/24 Valid RIR databaseRIPE 673 100% 66
195.62.32.0/24 Valid RIR databaseRIPE 673 100% 66
45.135.192.0/24 Valid RIR databaseRIPE 672 100% 66
45.153.33.0/24 Valid RIR databaseRIPE 672 100% 66
64.204.115.0/24 Valid RIR databaseARIN, RADB 672 100% 66
68.164.72.0/24 Valid RIR databaseARIN, RADB 672 100% 66
72.244.65.0/24 Valid RIR databaseARIN, RADB 672 100% 66
72.244.62.0/24 Valid RIR databaseARIN, RADB 671 100% 66
2a10:ca80::/48 Valid RIR databaseRIPE 631 99% 67
176.65.138.0/24 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

AS198584 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 25 are in fix.csv.

  • ROA: origin8
  • ROA: none4
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin45.87.248.0/24ROAs covering it name AS219335, not AS198584. If AS198584 should announce it, add a ROA for AS198584.2 of 673
Route object: none45.87.248.0/24Route objects for it name AS219335. Add a route object with origin AS198584 in the RIR database for the space.2 of 673
ROA: origin64.89.162.0/24ROAs covering it name AS51396, not AS198584. If AS198584 should announce it, add a ROA for AS198584.2 of 673
Route object: none64.89.162.0/24Route objects for it name AS51396, AS401626. Add a route object with origin AS198584 in the RIR database for the space.2 of 673
ROA: origin78.154.116.0/24ROAs covering it name AS834, not AS198584. If AS198584 should announce it, add a ROA for AS198584.1 of 673
Route object: none78.154.116.0/24Route objects for it name AS834. Add a route object with origin AS198584 in the RIR database for the space.1 of 673
ROA: origin151.242.148.0/24ROAs covering it name AS834, not AS198584. If AS198584 should announce it, add a ROA for AS198584.1 of 673
Route object: none151.242.148.0/24Route objects for it name AS834. Add a route object with origin AS198584 in the RIR database for the space.1 of 673
ROA: origin213.214.108.0/24ROAs covering it name AS834, not AS198584. If AS198584 should announce it, add a ROA for AS198584.1 of 673
Route object: none213.214.108.0/24Route objects for it name AS834. Add a route object with origin AS198584 in the RIR database for the space.1 of 673
ROA: origin217.60.27.0/24ROAs covering it name AS219506, not AS198584. If AS198584 should announce it, add a ROA for AS198584.1 of 673
Route object: none217.60.27.0/24Route objects for it name AS219506. Add a route object with origin AS198584 in the RIR database for the space.1 of 673
ROA: origin181.214.121.0/24ROAs covering it name AS834, not AS198584. If AS198584 should announce it, add a ROA for AS198584.171 of 673
Route object: RIR181.214.121.0/24Route object only in RADB. Add it in the RIR database for the space.171 of 673
ROA: origin85.133.216.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS198584 should announce it, add a ROA for AS198584.2 of 673
ROA: none176.65.128.0/24No ROA covers it. Add a ROA for AS198584, maxLength 24.673 of 673
ROA: none176.65.131.0/24No ROA covers it. Add a ROA for AS198584, maxLength 24.673 of 673
ROA: none176.65.135.0/24No ROA covers it. Add a ROA for AS198584, maxLength 24.673 of 673
ROA: none176.65.136.0/24No ROA covers it. Add a ROA for AS198584, maxLength 24.673 of 673

Route objects not announced

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

45.135.195.0/24RIPEValid
93.95.115.0/24RADB, RIPEValid
103.161.34.0/24APNICValid
103.161.35.0/24APNICValid
213.21.239.0/24RIPEValid
2a05:9080:5::/48RIPENo 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.