bgpreport

Network · data from 2026-11-12

AS4851 Host Networks

Registry name: HOSTNETWORKS-AS-AU-AP - Host Networks, AU · PeeringDB

13IPv4 routes 61.5% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
100Route objects not announced registered with origin AS4851, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4851, 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.
103.74.216.0/22 No ROA Other IRR onlyRADB 671 100% 67
103.196.148.0/22 No ROA Other IRR onlyRADB 671 100% 67
2402:f280::/32 No ROA Other IRR onlyALTDB 632 99% 67
117.120.40.0/21 No ROA RIR databaseRIPE 673 100% 67
202.174.96.0/20 No ROA RIR databaseRADB, RIPE 673 100% 67
119.148.64.0/19 No ROA RIR databaseRIPE 672 100% 67
103.74.217.0/24 Valid RIR databaseAPNIC 671 100% 67
103.74.218.0/23 Valid RIR databaseAPNIC 671 100% 67
103.77.144.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
103.77.144.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.194.229.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.206.187.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
202.128.106.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.77.146.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
2402:e400::/32 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:3280::/32 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS4851'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 109 are in fix.csv.

  • ROA: none6
  • Route object: RIR3
  • Route object: not announced100
ChangePrefix or setDetailFull-table peers
ROA: none103.74.216.0/22No ROA covers it. Add a ROA for AS4851, maxLength 22.671 of 673
Route object: RIR103.74.216.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.196.148.0/22No ROA covers it. Add a ROA for AS4851, maxLength 22.671 of 673
Route object: RIR103.196.148.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2402:f280::/32No ROA covers it. Add a ROA for AS4851, maxLength 32.632 of 636
Route object: RIR2402:f280::/32Route object only in ALTDB. Add it in the RIR database for the space.632 of 636
ROA: none117.120.40.0/21No ROA covers it. Add a ROA for AS4851, maxLength 21.673 of 673
ROA: none202.174.96.0/20No ROA covers it. Add a ROA for AS4851, maxLength 20.673 of 673
ROA: none119.148.64.0/19No ROA covers it. Add a ROA for AS4851, maxLength 19.672 of 673

Route objects not announced

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

103.61.228.0/23RADBNo ROA
103.61.228.0/24RADBNo ROA
103.61.229.0/24RADBNo ROA
103.73.82.0/24RADBNo ROA
103.82.155.0/24RADBNo ROA
111.118.220.0/23RADBNo ROA
111.118.222.0/23RADBNo ROA
117.120.40.0/22RADBNo ROA
117.120.44.0/22RADBNo ROA
119.148.64.0/20RADBNo ROA
119.148.64.0/21RADBNo ROA
119.148.66.0/24RADBNo ROA
119.148.72.0/24RADBNo ROA
119.148.73.0/24RADBNo ROA
119.148.74.0/23RADBNo ROA
119.148.76.0/22RADBNo ROA
119.148.80.0/24RADBNo ROA
119.148.81.0/24RADBNo ROA
119.148.82.0/23RADBNo ROA
119.148.84.0/22RADBNo ROA
119.148.88.0/21RADBNo ROA
125.253.94.0/23RADBNo ROA
125.253.94.0/24RADBNo ROA
125.253.95.0/24RADBNo ROA
192.189.148.0/24RADBNo ROA
202.94.32.0/20APNIC, RADBValid
202.174.96.0/21RADBNo ROA
202.174.96.0/22RADBNo ROA
202.174.96.0/23RADBNo ROA
202.174.96.0/24RADBNo ROA
202.174.97.0/24RADBNo ROA
202.174.98.0/23RADBNo ROA
202.174.98.0/24RADBNo ROA
202.174.99.0/24RADBNo ROA
202.174.100.0/22RADBNo ROA
202.174.100.0/23RADBNo ROA
202.174.100.0/24RADBNo ROA
202.174.101.0/24RADBNo ROA
202.174.102.0/23RADBNo ROA
202.174.102.0/24RADBNo ROA
202.174.103.0/24RADBNo ROA
202.174.104.0/21RADBNo ROA
202.174.104.0/22RADBNo ROA
202.174.104.0/23RADBNo ROA
202.174.104.0/24RADBNo ROA
202.174.105.0/24RADBNo ROA
202.174.106.0/23RADBNo ROA
202.174.106.0/24RADBNo ROA
202.174.107.0/24RADBNo ROA
202.174.108.0/22RADBNo ROA
202.174.108.0/23RADBNo ROA
202.174.108.0/24RADBNo ROA
202.174.109.0/24RADBNo ROA
202.174.110.0/23RADBNo ROA
202.174.110.0/24RADBNo ROA
202.174.111.0/24RADBNo ROA
203.24.63.0/24APNIC, RADBValid
203.26.113.0/24RADBNo ROA
203.27.44.0/24APNIC, RADBValid
203.27.106.0/23RADBNo ROA
203.27.106.0/24RADBNo ROA
203.27.107.0/24RADBNo ROA
203.29.208.0/23APNICValid
203.55.134.0/23APNIC, RADBValid
203.55.140.0/23RADBNo ROA
203.56.218.0/23RADBNo ROA
210.9.54.0/25RADBNo ROA
210.9.152.0/23RADBNo ROA
210.9.189.0/24RADBNo ROA
2402:e400::/33APNICValid
2402:e400::/34APNICValid
2402:e400::/35APNICValid
2402:e400::/36APNICValid
2402:e400:1000::/36APNICValid
2402:e400:2000::/35APNICValid
2402:e400:2000::/36APNICValid
2402:e400:3000::/36APNICValid
2402:e400:4000::/34APNICValid
2402:e400:4000::/35APNICValid
2402:e400:4000::/36APNICValid
2402:e400:5000::/36APNICValid
2402:e400:6000::/35APNICValid
2402:e400:6000::/36APNICValid
2402:e400:7000::/36APNICValid
2402:e400:8000::/33APNICValid
2402:e400:8000::/34APNICValid
2402:e400:8000::/35APNICValid
2402:e400:8000::/36APNICValid
2402:e400:9000::/36APNICValid
2402:e400:a000::/35APNICValid
2402:e400:a000::/36APNICValid
2402:e400:b000::/36APNICValid
2402:e400:c000::/34APNICValid
2402:e400:c000::/35APNICValid
2402:e400:c000::/36APNICValid
2402:e400:d000::/36APNICValid
2402:e400:e000::/35APNICValid
2402:e400:e000::/36APNICValid
2402:e400:f000::/36APNICValid
2407:a580::/32ALTDBNo 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.