bgpreport

Network · data from 2026-11-12

AS208164 Formicidae Holdings

Registry name: formicidae-holdings Formicidae Holdings B.V., NL · PeeringDB

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

Announced routes

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

2a0f:2880:400::/48 Invalid: maxLength Nonecovered by 2a0f:2880:400::/40 1 0%low visibility 1
193.27.91.0/24 Valid RIR databaseRIPE 671 100% 67
194.153.133.0/24 Valid RIR databaseRIPE 671 100% 67
2a0f:2880:400::/40 Valid RIR databaseRIPE 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS208164: AS-FORMICIDAE. 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 (AS208164 isn't in the set, or no route object for AS208164 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 objectsAS208164 in itNot covered
AS-FORMICIDAE RIPE 4110 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 2 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a0f:2880:400::/48ROA 2a0f:2880:400::/40 AS208164 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2a0f:2880:400::/48.1 of 636
Route object: none2a0f:2880:400::/48No route object for it. A route object for 2a0f:2880:400::/40 with origin AS208164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208164 in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS208164 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.