Network · data from 2026-11-12

AS52278 Fravatel

Registry name: AS52278 - FRAVATEL EIRL, PE · PeeringDB

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

9IPv6 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

4Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS52278, seen from no peer

Announced routes

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


190.105.240.0/20	Valid	RIR databaseLACNIC	671 100%	66
190.105.240.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.241.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.242.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.243.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.244.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.245.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.246.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.247.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.248.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.249.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.250.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.251.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.252.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.253.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.254.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.105.255.0/24	Valid	RIR databaseLACNIC	671 100%	66
2803:e990::/32	Valid	RIR databaseLACNIC	636 100%	67
2803:e990::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:2000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:4000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:6000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:8000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:a000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:c000::/35	Valid	RIR databaseLACNIC	636 100%	67
2803:e990:e000::/35	Valid	RIR databaseLACNIC	636 100%	67
190.105.240.0/22	Valid	RIR databaseLACNIC	1 0%low visibility	1
190.105.244.0/22	Valid	RIR databaseLACNIC	1 0%low visibility	1
190.105.248.0/23	Valid	RIR databaseLACNIC	1 0%low visibility	1
190.105.250.0/23	Valid	RIR databaseLACNIC	1 0%low visibility	1

190.105.240.0/20

Valid

RIR databaseLACNIC

671 100%

190.105.240.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.241.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.242.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.243.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.244.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.245.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.246.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.247.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.248.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.249.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.250.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.251.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.252.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.253.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.254.0/24

Valid

RIR databaseLACNIC

671 100%

190.105.255.0/24

Valid

RIR databaseLACNIC

671 100%

2803:e990::/32

Valid

RIR databaseLACNIC

636 100%

2803:e990::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:2000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:4000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:6000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:8000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:a000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:c000::/35

Valid

RIR databaseLACNIC

636 100%

2803:e990:e000::/35

Valid

RIR databaseLACNIC

636 100%

190.105.240.0/22

Valid

RIR databaseLACNIC

1 0%low visibility

190.105.244.0/22

Valid

RIR databaseLACNIC

1 0%low visibility

190.105.248.0/23

Valid

RIR databaseLACNIC

1 0%low visibility

190.105.250.0/23

Valid

RIR databaseLACNIC

1 0%low visibility

AS-SET

AS52278's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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