bgpreport

Network · data from 2026-11-12

AS49206 PeakFactory

Registry name: PeakFactory PeakFactory BV, NL · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
3Route objects not announced registered with origin AS49206, seen from no peer

Announced routes

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

185.41.49.0/24 Valid RIR databaseRIPE 673 100% 67
185.41.51.0/24 Valid RIR databaseRIPE 673 100% 67
185.24.175.0/24 Valid RIR databaseRIPE 672 100% 67
185.41.48.0/24 Valid RIR databaseRIPE 672 100% 67
185.41.50.0/24 Valid RIR databaseRIPE 672 100% 67
2a00:6fa0:4200::/40 Valid RIR databaseRIPE 635 100% 67
2a00:6fa0:3100::/40 Valid RIR databaseRIPE 634 100% 67
2a00:6fa0:ff00::/40 Valid RIR databaseRIPE 634 100% 67
83.118.224.0/22 Valid RIR databaseRIPE 149 22% 42

AS-SET

PeeringDB's irr_as_set for AS49206: AS-PEAKFACTORY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS49206 isn't in the set, or no route object for AS49206 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS49206 in itNot covered
AS-PEAKFACTORY RIPE 3125 Yes 0

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

  • Route object: not announced3

Route objects not announced

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

185.24.172.0/22RIPEValid
185.24.174.0/24RIPEValid
2a00:6fa0::/32RIPEValid

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.