bgpreport

Network · data from 2026-11-12

AS13448 WEBSENSE - Forcepoint, LLC

Registry name: WEBSENSE - Forcepoint, LLC, US · not in PeeringDB

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

Announced routes

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

2620:12c:b018::/48 No ROA None 635 100% 67
204.15.64.0/23 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
208.80.196.0/24 No ROA Other IRR onlyALTDB, RIPE-NONAUTH 673 100% 67
157.167.1.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
157.167.3.0/24 Valid RIR databaseRADB, RIPE 673 100% 67

AS-SET

AS13448 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 38 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none2620:12c:b018::/48No ROA covers it. Add a ROA for AS13448, maxLength 48.635 of 636
Route object: none2620:12c:b018::/48No route object for it. Add a route object with origin AS13448 in the RIR database for the space.635 of 636
ROA: none204.15.64.0/23No ROA covers it. Add a ROA for AS13448, maxLength 23.673 of 673
Route object: RIR204.15.64.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none208.80.196.0/24No ROA covers it. Add a ROA for AS13448, maxLength 24.673 of 673
Route object: RIR208.80.196.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

86.111.218.0/23RIPENo ROA
86.111.218.0/24RIPENo ROA
86.111.219.0/24RADB, RIPENo ROA
86.111.220.0/23RIPENo ROA
157.167.0.0/24RIPEInvalid: origin
157.167.2.0/24RADB, RIPENo ROA
185.101.80.0/24RADBNo ROA
192.132.210.0/24RIPE-NONAUTHNo ROA
204.15.64.0/21RIPE-NONAUTHNo ROA
204.15.64.0/24RIPE-NONAUTHNo ROA
204.15.65.0/24RIPE-NONAUTHNo ROA
204.15.66.0/24ALTDB, RIPE-NONAUTHNo ROA
204.15.67.0/24ALTDB, RIPE-NONAUTHNo ROA
204.15.68.0/24RIPE-NONAUTHNo ROA
204.15.69.0/24ALTDB, RIPE-NONAUTHNo ROA
204.15.70.0/23RIPE-NONAUTHNo ROA
204.15.70.0/24RIPE-NONAUTHNo ROA
204.15.71.0/24RIPE-NONAUTHNo ROA
208.80.192.0/21RIPE-NONAUTHNo ROA
208.80.192.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.193.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.194.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.195.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.197.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.198.0/24ALTDB, RIPE-NONAUTHNo ROA
208.80.199.0/24ALTDB, RIPE-NONAUTHNo ROA
2001:4010:fff0::/44RIPEInvalid: origin
2620:0:c0::/48RIPE-NONAUTHNo ROA
2620:12c:b004::/48RADBNo ROA
2620:12c:b052::/48RADBNo ROA
2620:12c:b067::/48RADBNo ROA
2620:12c:b068::/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.