bgpreport

Network · data from 2026-11-12

AS53768 Laboratory Corporation of America

Registry name: LABCORP - Laboratory Corporation of America, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53768, 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.
12.39.198.0/23 No ROA None 673 100% 70
162.134.250.0/24 No ROA None 673 100% 67
12.35.188.0/22 No ROA RIR databaseARIN 673 100% 70
12.145.88.0/21 No ROA RIR databaseARIN 673 100% 70
162.134.32.0/20 Valid RIR databaseARIN 673 100% 70
162.134.48.0/20 Valid RIR databaseARIN 673 100% 70
162.134.64.0/20 Valid RIR databaseARIN 673 100% 70
162.134.80.0/22 Valid RIR databaseARIN 673 100% 70
162.134.84.0/23 Valid RIR databaseARIN 673 100% 70
162.134.86.0/23 Valid RIR databaseARIN 673 100% 70
162.134.88.0/21 Valid RIR databaseARIN 673 100% 70
162.134.96.0/23 Valid RIR databaseARIN 673 100% 70
162.134.98.0/23 Valid RIR databaseARIN 673 100% 70
162.134.100.0/23 Valid RIR databaseARIN 673 100% 70
162.134.102.0/23 Valid RIR databaseARIN 673 100% 70
162.134.160.0/20 Valid RIR databaseARIN 673 100% 70

AS-SET

AS53768'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 10 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none12.39.198.0/23No ROA covers it. Add a ROA for AS53768, maxLength 23.673 of 673
Route object: none12.39.198.0/23No route object for it. Add a route object with origin AS53768 in the RIR database for the space.673 of 673
ROA: none162.134.250.0/24No ROA covers it. Add a ROA for AS53768, maxLength 24.673 of 673
Route object: none162.134.250.0/24No route object for it. Add a route object with origin AS53768 in the RIR database for the space.673 of 673
ROA: none12.35.188.0/22No ROA covers it. Add a ROA for AS53768, maxLength 22.673 of 673
ROA: none12.145.88.0/21No ROA covers it. Add a ROA for AS53768, maxLength 21.673 of 673

Route objects not announced

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

162.134.54.0/24ARINValid
162.134.80.0/20ARINValid
162.134.128.0/24ARINValid
209.194.235.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.