bgpreport

Network · data from 2026-11-12

AS400985 TRCAS - Three Rivers Casino and Resort

Registry name: TRCAS - Three Rivers Casino and Resort, US · not in PeeringDB

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

Announced routes

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

2602:f60c:9::/48 No ROA Other IRR onlyRADB 636 100% 69
2602:f60c:f::/48 No ROA Other IRR onlyRADB 636 100% 69
71.92.140.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS400985 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 4 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2602:f60c:9::/48No ROA covers it. Add a ROA for AS400985, maxLength 48.636 of 636
Route object: RIR2602:f60c:9::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2602:f60c:f::/48No ROA covers it. Add a ROA for AS400985, maxLength 48.636 of 636
Route object: RIR2602:f60c:f::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS400985 is announced.

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.