bgpreport

Network · data from 2026-11-12

AS1004 Ambyre Global

Registry name: AMBYRE - Ambyre LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1004, 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.
2a10:eac0::/29 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
209.112.91.0/24 No ROA RIR databaseARIN 669 99% 67
209.112.88.0/24 Valid RIR databaseARIN 672 100% 67
209.112.90.0/24 Valid RIR databaseARIN 669 99% 67
2602:fba3:302::/48 Valid RIR databaseARIN 635 100% 69
2602:fba3:401::/48 Valid RIR databaseARIN 635 100% 67
2602:fba3:402::/48 Valid RIR databaseARIN 635 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a10:eac0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS1004 should announce it, add a ROA for AS1004.1 of 636
ROA: none209.112.91.0/24No ROA covers it. Add a ROA for AS1004, maxLength 24.669 of 673

Route objects not announced

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

142.248.80.0/22ARINValid
2a0a:6040:4d00::/40RIPENo 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.