bgpreport

Network · data from 2026-11-12

AS23296 LINCARE-HOLDINGS-INC - LINCARE INC

Registry name: LINCARE-HOLDINGS-INC - LINCARE INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23296, 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.
208.81.28.0/24 No ROA Other origin onlycovered by 208.81.28.0/23 673 100% 67
208.81.29.0/24 No ROA Nonecovered by 208.81.28.0/23 673 100% 67
208.81.30.0/24 No ROA Nonecovered by 208.81.30.0/23 673 100% 67
208.81.31.0/24 No ROA Other origin onlycovered by 208.81.30.0/23 673 100% 67

AS-SET

AS23296 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none208.81.28.0/24No ROA covers it. Add a ROA for AS23296, maxLength 24.673 of 673
Route object: none208.81.28.0/24Route objects for it name AS13343, AS33363. A route object for 208.81.28.0/23 with origin AS23296 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23296 in the RIR database for the space.673 of 673
ROA: none208.81.29.0/24No ROA covers it. Add a ROA for AS23296, maxLength 24.673 of 673
Route object: none208.81.29.0/24No route object for it. A route object for 208.81.28.0/23 with origin AS23296 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23296 in the RIR database for the space.673 of 673
ROA: none208.81.30.0/24No ROA covers it. Add a ROA for AS23296, maxLength 24.673 of 673
Route object: none208.81.30.0/24No route object for it. A route object for 208.81.30.0/23 with origin AS23296 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23296 in the RIR database for the space.673 of 673
ROA: none208.81.31.0/24No ROA covers it. Add a ROA for AS23296, maxLength 24.673 of 673
Route object: none208.81.31.0/24Route objects for it name AS36363. A route object for 208.81.30.0/23 with origin AS23296 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23296 in the RIR database for the space.673 of 673

Route objects not announced

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

8.42.201.0/24RADBNo ROA
208.81.28.0/23RADBNo ROA
208.81.30.0/23RADBNo 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.