bgpreport

Network · data from 2026-11-12

AS36504 TRIPLE8 - Triple8 Network, Inc.

Registry name: TRIPLE8 - Triple8 Network, Inc., US · not in PeeringDB

9IPv4 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
8Route objects not announced registered with origin AS36504, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36504, 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.
74.112.248.0/23 Valid RIR databaseARIN, RADB 673 100% 67
74.112.250.0/23 Valid RIR databaseARIN 673 100% 67
208.67.224.0/22 Valid RIR databaseARIN, RADB 673 100% 67
208.73.48.0/24 Valid RIR databaseARIN, RADB 673 100% 67
208.73.49.0/24 Valid RIR databaseARIN 673 100% 67
208.80.182.0/24 Valid RIR databaseARIN, RADB 673 100% 67
74.112.252.0/24 Valid RIR databaseARIN 672 100% 67
74.112.253.0/24 Valid RIR databaseARIN 672 100% 67
74.112.255.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS36504 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 8 are in fix.csv.

  • Route object: not announced8

Route objects not announced

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

74.112.248.0/21RADBNo ROA
74.112.248.0/22RADBNo ROA
208.73.48.0/23RADBNo ROA
208.73.50.0/23RADBNo ROA
208.80.180.0/24RADBNo ROA
208.80.181.0/24RADBNo ROA
208.80.183.0/24RADBNo ROA
2604:dac0::/32RADBNo 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.