bgpreport

Network · data from 2026-11-12

AS53824 Liquid Web, L.L.C

Registry name: LIQUIDWEB - Liquid Web, L.L.C, US · PeeringDB

6IPv4 routes 0.0% RPKI valid · 83.3% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
93Route objects not announced registered with origin AS53824, seen from no peer

Announced routes

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

207.246.240.0/21 No ROA Nonecovered by 207.246.240.0/20 672 100% 67
50.56.148.0/22 No ROA Other IRR onlyRADB 672 100% 67
159.135.0.0/19 No ROA Other IRR onlyRADB 672 100% 67
159.135.32.0/20 No ROA Other IRR onlyRADB 672 100% 67
50.28.96.0/19 No ROA Other IRR onlyRADB 670 100% 67
98.129.229.0/24 No ROA Other IRR onlyRADB 669 99% 67
2604:d700::/32 No ROA Other IRR onlyRADB 635 100% 67
2607:fad0:40::/44 No ROA Other IRR onlyRADB 635 100% 67
2607:fad0:4000::/36 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS53824'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 111 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced93
ChangePrefix or setDetailFull-table peers
ROA: none207.246.240.0/21No ROA covers it. Add a ROA for AS53824, maxLength 21.672 of 673
Route object: none207.246.240.0/21No route object for it. A route object for 207.246.240.0/20 with origin AS53824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53824 in the RIR database for the space.672 of 673
ROA: none50.56.148.0/22No ROA covers it. Add a ROA for AS53824, maxLength 22.672 of 673
Route object: RIR50.56.148.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none159.135.0.0/19No ROA covers it. Add a ROA for AS53824, maxLength 19.672 of 673
Route object: RIR159.135.0.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none159.135.32.0/20No ROA covers it. Add a ROA for AS53824, maxLength 20.672 of 673
Route object: RIR159.135.32.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none50.28.96.0/19No ROA covers it. Add a ROA for AS53824, maxLength 19.670 of 673
Route object: RIR50.28.96.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none98.129.229.0/24No ROA covers it. Add a ROA for AS53824, maxLength 24.669 of 673
Route object: RIR98.129.229.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2604:d700::/32No ROA covers it. Add a ROA for AS53824, maxLength 32.635 of 636
Route object: RIR2604:d700::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2607:fad0:40::/44No ROA covers it. Add a ROA for AS53824, maxLength 44.635 of 636
Route object: RIR2607:fad0:40::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2607:fad0:4000::/36No ROA covers it. Add a ROA for AS53824, maxLength 36.635 of 636
Route object: RIR2607:fad0:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

50.28.96.0/24RADBNo ROA
50.28.97.0/24RADBNo ROA
50.28.98.0/24RADBNo ROA
50.28.99.0/24RADBNo ROA
50.28.100.0/24RADBNo ROA
50.28.101.0/24RADBNo ROA
50.28.102.0/24RADBNo ROA
50.28.103.0/24RADBNo ROA
50.28.104.0/24RADBNo ROA
50.28.105.0/24RADBNo ROA
50.28.106.0/24RADBNo ROA
50.28.107.0/24RADBNo ROA
50.28.108.0/24RADBNo ROA
50.28.109.0/24RADBNo ROA
50.28.110.0/24RADBNo ROA
50.28.111.0/24RADBNo ROA
50.28.112.0/24RADBNo ROA
50.28.113.0/24RADBNo ROA
50.28.114.0/24RADBNo ROA
50.28.115.0/24RADBNo ROA
50.28.116.0/24RADBNo ROA
50.28.117.0/24RADBNo ROA
50.28.118.0/24RADBNo ROA
50.28.119.0/24RADBNo ROA
50.28.120.0/24RADBNo ROA
50.28.121.0/24RADBNo ROA
50.28.122.0/24RADBNo ROA
50.28.123.0/24RADBNo ROA
50.28.124.0/24RADBNo ROA
50.28.125.0/24RADBNo ROA
50.28.126.0/24RADBNo ROA
50.28.127.0/24RADBNo ROA
50.56.148.0/24RADBNo ROA
50.56.149.0/24RADBNo ROA
50.56.150.0/24RADBNo ROA
50.56.151.0/24RADBNo ROA
159.135.0.0/24RADBNo ROA
159.135.1.0/24RADBNo ROA
159.135.2.0/24RADBNo ROA
159.135.3.0/24RADBNo ROA
159.135.4.0/24RADBNo ROA
159.135.5.0/24RADBNo ROA
159.135.6.0/24RADBNo ROA
159.135.7.0/24RADBNo ROA
159.135.8.0/24RADBNo ROA
159.135.9.0/24RADBNo ROA
159.135.10.0/24RADBNo ROA
159.135.11.0/24RADBNo ROA
159.135.12.0/24RADBNo ROA
159.135.13.0/24RADBNo ROA
159.135.14.0/24RADBNo ROA
159.135.15.0/24RADBNo ROA
159.135.16.0/24RADBNo ROA
159.135.17.0/24RADBNo ROA
159.135.18.0/24RADBNo ROA
159.135.19.0/24RADBNo ROA
159.135.20.0/24RADBNo ROA
159.135.21.0/24RADBNo ROA
159.135.22.0/24RADBNo ROA
159.135.23.0/24RADBNo ROA
159.135.24.0/24RADBNo ROA
159.135.25.0/24RADBNo ROA
159.135.26.0/24RADBNo ROA
159.135.27.0/24RADBNo ROA
159.135.28.0/24RADBNo ROA
159.135.29.0/24RADBNo ROA
159.135.30.0/24RADBNo ROA
159.135.31.0/24RADBNo ROA
159.135.32.0/24RADBNo ROA
159.135.33.0/24RADBNo ROA
159.135.34.0/24RADBNo ROA
159.135.35.0/24RADBNo ROA
159.135.36.0/24RADBNo ROA
159.135.37.0/24RADBNo ROA
159.135.38.0/24RADBNo ROA
159.135.39.0/24RADBNo ROA
159.135.40.0/24RADBNo ROA
159.135.41.0/24RADBNo ROA
159.135.42.0/24RADBNo ROA
159.135.43.0/24RADBNo ROA
159.135.44.0/24RADBNo ROA
159.135.45.0/24RADBNo ROA
159.135.46.0/24RADBNo ROA
159.135.47.0/24RADBNo ROA
207.246.240.0/20RADBNo ROA
207.246.240.0/24RADBNo ROA
207.246.241.0/24RADBNo ROA
207.246.242.0/24RADBNo ROA
207.246.243.0/24RADBNo ROA
207.246.244.0/24RADBNo ROA
207.246.245.0/24RADBNo ROA
207.246.246.0/24RADBNo ROA
207.246.247.0/24RADBNo 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.