bgpreport

Network · data from 2026-11-12

AS213094 Full Fibre Ltd

Registry name: FullFibre Full Fibre Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213094, 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.74.52.0/23 Invalid: origin Other origin only 2 0%low visibility 2
149.13.208.0/20 No ROA None 672 100% 67
185.252.160.0/23 No ROA None 2 0%low visibility 2
154.61.152.0/22 No ROA Other IRR onlyRADB 672 100% 67
84.18.224.0/22 Valid RIR databaseRIPE 672 100% 67
84.18.240.0/22 Valid RIR databaseRIPE 672 100% 67
89.22.196.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
94.103.240.0/22 Valid RIR databaseRIPE 672 100% 67
193.3.34.0/24 Valid RIR databaseRIPE 672 100% 67
2a0b:cc80::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS213094: AS-FULLFIBRE. 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 (AS213094 isn't in the set, or no route object for AS213094 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 objectsAS213094 in itNot covered
AS-FULLFIBRE RIPE 217 Yes 3

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

  • ROA: origin1
  • ROA: none3
  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin185.74.52.0/23ROAs covering it name AS834, not AS213094. If AS213094 should announce it, add a ROA for AS213094.2 of 673
Route object: none185.74.52.0/23Route objects for it name AS834. Add a route object with origin AS213094 in the RIR database for the space.2 of 673
ROA: none149.13.208.0/20No ROA covers it. Add a ROA for AS213094, maxLength 20.672 of 673
Route object: none149.13.208.0/20No route object for it. Add a route object with origin AS213094 in the RIR database for the space.672 of 673
ROA: none185.252.160.0/23No ROA covers it. Add a ROA for AS213094, maxLength 23.2 of 673
Route object: none185.252.160.0/23No route object for it. Add a route object with origin AS213094 in the RIR database for the space.2 of 673
ROA: none154.61.152.0/22No ROA covers it. Add a ROA for AS213094, maxLength 22.672 of 673
Route object: RIR154.61.152.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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