bgpreport

Network · data from 2026-11-12

AS5 SYMBOLICS - WFA Group LLC

Registry name: SYMBOLICS - WFA Group LLC, US · not in PeeringDB

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

Announced routes

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

116.212.177.0/24 Invalid: origin Other origin only 82 12% 45
103.158.65.0/24 Invalid: origin Other origin only 16 2%low visibility 15
116.212.179.0/24 Invalid: origin Other origin only 2 0%low visibility 1
203.15.16.0/24 Invalid: origin Other origin only 2 0%low visibility 1
45.178.213.0/24 No ROA Other origin only 664 99% 67
38.109.201.0/24 No ROA Other origin only 319 47% 59
38.109.226.0/24 No ROA Other origin only 319 47% 59
103.148.204.0/24 No ROA Other origin only 144 21% 48
167.253.45.0/24 No ROA Other origin only 73 11% 36

AS-SET

AS5 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 19 are in fix.csv.

  • ROA: origin4
  • ROA: none5
  • Route object: none9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin116.212.177.0/24ROAs covering it name AS55839, not AS5. If AS5 should announce it, add a ROA for AS5.82 of 673
Route object: none116.212.177.0/24Route objects for it name AS55839. Add a route object with origin AS5 in the RIR database for the space.82 of 673
ROA: origin103.158.65.0/24ROAs covering it name AS55470, AS134320, not AS5. If AS5 should announce it, add a ROA for AS5.16 of 673
Route object: none103.158.65.0/24Route objects for it name AS55470, AS134320. Add a route object with origin AS5 in the RIR database for the space.16 of 673
ROA: origin116.212.179.0/24ROAs covering it name AS55839, not AS5. If AS5 should announce it, add a ROA for AS5.2 of 673
Route object: none116.212.179.0/24Route objects for it name AS55839. Add a route object with origin AS5 in the RIR database for the space.2 of 673
ROA: origin203.15.16.0/24ROAs covering it name AS134320, not AS5. If AS5 should announce it, add a ROA for AS5.2 of 673
Route object: none203.15.16.0/24Route objects for it name AS134320. Add a route object with origin AS5 in the RIR database for the space.2 of 673
ROA: none45.178.213.0/24No ROA covers it. Add a ROA for AS5, maxLength 24.664 of 673
Route object: none45.178.213.0/24Route objects for it name AS269111. Add a route object with origin AS5 in the RIR database for the space.664 of 673
ROA: none38.109.201.0/24No ROA covers it. Add a ROA for AS5, maxLength 24.319 of 673
Route object: none38.109.201.0/24Route objects for it name AS26550. Add a route object with origin AS5 in the RIR database for the space.319 of 673
ROA: none38.109.226.0/24No ROA covers it. Add a ROA for AS5, maxLength 24.319 of 673
Route object: none38.109.226.0/24Route objects for it name AS26550. Add a route object with origin AS5 in the RIR database for the space.319 of 673
ROA: none103.148.204.0/24No ROA covers it. Add a ROA for AS5, maxLength 24.144 of 673
Route object: none103.148.204.0/24Route objects for it name AS55470, AS134320. Add a route object with origin AS5 in the RIR database for the space.144 of 673
ROA: none167.253.45.0/24No ROA covers it. Add a ROA for AS5, maxLength 24.73 of 673
Route object: none167.253.45.0/24Route objects for it name AS395240. Add a route object with origin AS5 in the RIR database for the space.73 of 673

Route objects not announced

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

192.189.195.0/24ARINValid

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.