Network · data from 2026-11-12

AS218964 QUATTRO-AS QUATTRO APPS LTD

Registry name: QUATTRO-AS QUATTRO APPS LTD, GB · not in PeeringDB

28IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

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

13Route objects not announced registered with origin AS218964, seen from no peer

Announced routes

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


89.125.99.0/24	Valid	RIR databaseRIPE	673 100%	67
89.125.101.0/24	Valid	RIR databaseRIPE	673 100%	67
89.125.149.0/24	Valid	RIR databaseRIPE	673 100%	67
104.250.254.0/24	Valid	RIR databaseARIN	673 100%	67
132.243.232.0/24	Valid	RIR databaseRIPE	673 100%	67
132.243.233.0/24	Valid	RIR databaseRIPE	673 100%	67
139.28.215.0/24	Valid	RIR databaseRIPE	673 100%	67
179.254.76.0/24	Valid	RIR databaseRIPE	673 100%	67
179.254.90.0/24	Valid	RIR databaseRIPE	673 100%	66
179.254.93.0/24	Valid	RIR databaseRIPE	673 100%	67
179.254.98.0/24	Valid	RIR databaseRIPE	673 100%	67
185.184.24.0/24	Valid	RIR databaseRIPE	673 100%	67
31.77.5.0/24	Valid	RIR databaseRIPE	672 100%	67
89.125.158.0/24	Valid	RIR databaseRIPE	672 100%	67
166.88.172.0/24	Valid	RIR databaseARIN	672 100%	66
179.254.96.0/24	Valid	RIR databaseRIPE	672 100%	67
13.143.231.0/24	Valid	RIR databaseRIPE	671 100%	67
31.77.3.0/24	Valid	RIR databaseRIPE	671 100%	68
31.77.4.0/24	Valid	RIR databaseRIPE	671 100%	67
31.77.52.0/24	Valid	RIR databaseRIPE	671 100%	67
89.125.142.0/24	Valid	RIR databaseRIPE	671 100%	68
104.250.252.0/24	Valid	RIR databaseARIN	671 100%	68
132.243.205.0/24	Valid	RIR databaseRIPE	671 100%	67
166.88.185.0/24	Valid	RIR databaseARIN	671 100%	67
179.254.78.0/24	Valid	RIR databaseRIPE	671 100%	67
89.125.157.0/24	Valid	RIR databaseRIPE	670 100%	67
166.88.229.0/24	Valid	RIR databaseARIN	670 100%	67
13.143.209.0/24	Valid	RIR databaseRIPE	655 97%	67

AS-SET

AS218964 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.

Route object: not announced13

Route objects not announced

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


13.143.230.0/24	RIPE	Valid
31.77.74.0/24	RIPE	Valid
139.28.212.0/24	RIPE	Valid
139.28.213.0/24	RIPE	Valid
139.28.214.0/24	RIPE	Valid
179.254.88.0/24	RIPE	Valid
179.254.89.0/24	RIPE	Valid
185.119.82.0/24	RIPE	Valid
201.8.75.0/24	RIPE	Valid
201.8.76.0/24	RIPE	Valid
201.8.77.0/24	RIPE	Valid
201.8.78.0/24	RIPE	Valid
201.8.79.0/24	RIPE	Valid

13.143.230.0/24

RIPE

Valid

31.77.74.0/24

RIPE

Valid

139.28.212.0/24

RIPE

Valid

139.28.213.0/24

RIPE

Valid

139.28.214.0/24

RIPE

Valid

179.254.88.0/24

RIPE

Valid

179.254.89.0/24

RIPE

Valid

185.119.82.0/24

RIPE

Valid

201.8.75.0/24

RIPE

Valid

201.8.76.0/24

RIPE

Valid

201.8.77.0/24

RIPE

Valid

201.8.78.0/24

RIPE

Valid

201.8.79.0/24

RIPE

Valid

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.