bgpreport

Network · data from 2026-11-12

AS43685 Mean Servers

Registry name: peaktera-eu Peaktera Holdings Corporation, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43685, 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.
199.91.104.0/22 Invalid: origin RIR databaseARIN 0 0%low visibility 1
2a0b:2281::/32 Valid RIR databaseRIPE 634 100% 69
2a0b:2282::/31 Valid RIR databaseRIPE 633 100% 69
2a0b:2284::/30 Valid RIR databaseRIPE 633 100% 69

AS-SET

AS43685'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 2 are in fix.csv.

  • ROA: origin1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin199.91.104.0/22ROAs covering it name AS32931, not AS43685. If AS43685 should announce it, add a ROA for AS43685.0 of 673

Route objects not announced

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

2a0b:2280::/29RIPEValid

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.