bgpreport

Network · data from 2026-11-12

AS399480 TI-GARLAND-QX-HUB - Texas Instruments Incorporated

Registry name: TI-GARLAND-QX-HUB - Texas Instruments Incorporated, US · not in PeeringDB

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

Announced routes

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

192.228.64.0/24 Valid RIR databaseARIN 673 100% 67
192.228.65.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS399480 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 26 are in fix.csv.

  • Route object: not announced26

Route objects not announced

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

192.138.118.0/23APNICValid
192.138.118.0/24APNICValid
192.138.119.0/24APNICValid
192.138.120.0/22APNICValid
192.138.120.0/23APNICValid
192.138.120.0/24APNICValid
192.138.121.0/24APNICValid
192.138.122.0/23APNICValid
192.138.122.0/24APNICValid
192.138.123.0/24APNICValid
192.138.124.0/23APNICValid
192.138.124.0/24APNICValid
192.138.125.0/24APNICValid
192.153.221.0/24APNICValid
192.153.222.0/23APNICValid
192.153.222.0/24APNICValid
192.153.223.0/24APNICValid
192.153.224.0/22APNICValid
192.153.224.0/23APNICValid
192.153.224.0/24APNICValid
192.153.225.0/24APNICValid
192.153.226.0/23APNICValid
192.153.226.0/24APNICValid
192.153.227.0/24APNICValid
192.153.228.0/24APNICValid
192.228.64.0/23ARINValid

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.