bgpreport

Network · data from 2026-11-12

AS11917 META-02

Registry name: WHATSAPP - WhatsApp, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11917, 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.
57.136.20.0/22 No ROA Other IRR onlyRADB 672 100% 67
57.136.20.0/24 No ROA Other IRR onlyRADB 672 100% 67
2a03:2884:14::/46 No ROA Other IRR onlyRADB 635 100% 67
2a03:2884:14::/48 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS11917'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 144 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced136
ChangePrefix or setDetailFull-table peers
ROA: none57.136.20.0/22No ROA covers it. Add a ROA for AS11917, maxLength 22.672 of 673
Route object: RIR57.136.20.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none57.136.20.0/24No ROA covers it. Add a ROA for AS11917, maxLength 24.672 of 673
Route object: RIR57.136.20.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2a03:2884:14::/46No ROA covers it. Add a ROA for AS11917, maxLength 46.635 of 636
Route object: RIR2a03:2884:14::/46Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2a03:2884:14::/48No ROA covers it. Add a ROA for AS11917, maxLength 48.635 of 636
Route object: RIR2a03:2884:14::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

57.136.0.0/22RADBNo ROA
57.136.0.0/24RADBNo ROA
57.136.1.0/24RADBNo ROA
57.136.2.0/24RADBNo ROA
57.136.3.0/24RADBNo ROA
57.136.4.0/22RADBNo ROA
57.136.4.0/24RADBNo ROA
57.136.5.0/24RADBNo ROA
57.136.6.0/24RADBNo ROA
57.136.7.0/24RADBNo ROA
57.136.8.0/22RADBNo ROA
57.136.8.0/24RADBNo ROA
57.136.9.0/24RADBNo ROA
57.136.10.0/24RADBNo ROA
57.136.11.0/24RADBNo ROA
57.136.12.0/22RADBNo ROA
57.136.12.0/24RADBNo ROA
57.136.13.0/24RADBNo ROA
57.136.14.0/24RADBNo ROA
57.136.15.0/24RADBNo ROA
57.136.16.0/22RADBNo ROA
57.136.16.0/24RADBNo ROA
57.136.17.0/24RADBNo ROA
57.136.18.0/24RADBNo ROA
57.136.19.0/24RADBNo ROA
57.136.21.0/24RADBNo ROA
57.136.22.0/24RADBNo ROA
57.136.23.0/24RADBNo ROA
57.136.24.0/22RADBNo ROA
57.136.24.0/24RADBNo ROA
57.136.25.0/24RADBNo ROA
57.136.26.0/24RADBNo ROA
57.136.27.0/24RADBNo ROA
57.136.28.0/22RADBNo ROA
57.136.28.0/24RADBNo ROA
57.136.29.0/24RADBNo ROA
57.136.30.0/24RADBNo ROA
57.136.31.0/24RADBNo ROA
57.136.32.0/22RADBNo ROA
57.136.32.0/24RADBNo ROA
57.136.33.0/24RADBNo ROA
57.136.34.0/24RADBNo ROA
57.136.35.0/24RADBNo ROA
57.136.36.0/22RADBNo ROA
57.136.36.0/24RADBNo ROA
57.136.37.0/24RADBNo ROA
57.136.38.0/24RADBNo ROA
57.136.39.0/24RADBNo ROA
57.136.40.0/22RADBNo ROA
57.136.40.0/24RADBNo ROA
57.136.41.0/24RADBNo ROA
57.136.42.0/24RADBNo ROA
57.136.43.0/24RADBNo ROA
57.136.44.0/22RADBNo ROA
57.136.44.0/24RADBNo ROA
57.136.45.0/24RADBNo ROA
57.136.46.0/24RADBNo ROA
57.136.47.0/24RADBNo ROA
57.136.48.0/22RADBNo ROA
57.136.48.0/24RADBNo ROA
57.136.49.0/24RADBNo ROA
57.136.50.0/24RADBNo ROA
57.136.51.0/24RADBNo ROA
66.111.48.0/22ARIN, RADBValid
66.111.48.0/24RADBValid
66.111.49.0/24RADBValid
66.111.50.0/24RADBValid
66.111.51.0/24RADBValid
2620:13e:1000::/44ARIN, RADBValid
2620:13e:100c::/48RADBValid
2620:13e:100d::/48RADBValid
2620:13e:100e::/48RADBValid
2620:13e:100f::/48RADBValid
2a03:2884::/46RADBNo ROA
2a03:2884::/48RADBNo ROA
2a03:2884:1::/48RADBNo ROA
2a03:2884:2::/48RADBNo ROA
2a03:2884:3::/48RADBNo ROA
2a03:2884:4::/46RADBNo ROA
2a03:2884:4::/48RADBNo ROA
2a03:2884:5::/48RADBNo ROA
2a03:2884:6::/48RADBNo ROA
2a03:2884:7::/48RADBNo ROA
2a03:2884:8::/46RADBNo ROA
2a03:2884:8::/48RADBNo ROA
2a03:2884:9::/48RADBNo ROA
2a03:2884:a::/48RADBNo ROA
2a03:2884:b::/48RADBNo ROA
2a03:2884:c::/46RADBNo ROA
2a03:2884:c::/48RADBNo ROA
2a03:2884:d::/48RADBNo ROA
2a03:2884:e::/48RADBNo ROA
2a03:2884:f::/48RADBNo ROA
2a03:2884:10::/46RADBNo ROA
2a03:2884:10::/48RADBNo ROA
2a03:2884:11::/48RADBNo ROA
2a03:2884:12::/48RADBNo ROA
2a03:2884:13::/48RADBNo ROA
2a03:2884:15::/48RADBNo ROA
2a03:2884:16::/48RADBNo ROA
2a03:2884:17::/48RADBNo ROA
2a03:2884:18::/46RADBNo ROA
2a03:2884:18::/48RADBNo ROA
2a03:2884:19::/48RADBNo ROA
2a03:2884:1a::/48RADBNo ROA
2a03:2884:1b::/48RADBNo ROA
2a03:2884:1c::/46RADBNo ROA
2a03:2884:1c::/48RADBNo ROA
2a03:2884:1d::/48RADBNo ROA
2a03:2884:1e::/48RADBNo ROA
2a03:2884:1f::/48RADBNo ROA
2a03:2884:20::/46RADBNo ROA
2a03:2884:20::/48RADBNo ROA
2a03:2884:21::/48RADBNo ROA
2a03:2884:22::/48RADBNo ROA
2a03:2884:23::/48RADBNo ROA
2a03:2884:24::/46RADBNo ROA
2a03:2884:24::/48RADBNo ROA
2a03:2884:25::/48RADBNo ROA
2a03:2884:26::/48RADBNo ROA
2a03:2884:27::/48RADBNo ROA
2a03:2884:28::/46RADBNo ROA
2a03:2884:28::/48RADBNo ROA
2a03:2884:29::/48RADBNo ROA
2a03:2884:2a::/48RADBNo ROA
2a03:2884:2b::/48RADBNo ROA
2a03:2884:2c::/46RADBNo ROA
2a03:2884:2c::/48RADBNo ROA
2a03:2884:2d::/48RADBNo ROA
2a03:2884:2e::/48RADBNo ROA
2a03:2884:2f::/48RADBNo ROA
2a03:2884:30::/46RADBNo ROA
2a03:2884:30::/48RADBNo ROA
2a03:2884:31::/48RADBNo ROA
2a03:2884:32::/48RADBNo ROA
2a03:2884:33::/48RADBNo 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.