bgpreport

Network · data from 2026-11-12

AS213462 FibreConnect

Registry name: FibreConnect-AS FibreConnect S.p.A., IT · PeeringDB

2IPv4 routes 100.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 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 AS213462, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213462, 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.
62.50.143.0/24 Valid Nonecovered by 62.50.140.0/22 1 0%low visibility 4
62.50.140.0/22 Valid RIR databaseRIPE 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS213462: AS213462:AS-FIBRECONNECT. 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 (AS213462 isn't in the set, or no route object for AS213462 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 objectsAS213462 in itNot covered
AS213462:AS-FIBRECONNECT RIPE1 member set in no database: AS213462:AS-MAIN 332,066 No 2

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: none1
  • AS-SET: own ASN1
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none62.50.143.0/24No route object for it. A route object for 62.50.140.0/22 with origin AS213462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213462 in the RIR database for the space.1 of 673
AS-SET: own ASNAS213462:AS-FIBRECONNECTAS213462 isn't in AS213462:AS-FIBRECONNECT (RIPE) once expanded. Add AS213462 to it.
AS-SET: missing memberAS213462:AS-FIBRECONNECTAS213462:AS-FIBRECONNECT (RIPE) lists AS213462:AS-MAIN; no IRR database read has it.

Route objects not announced

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