Network · data from 2026-11-12

AS266418 AS266418 - SERVTEL EIRELI

Registry name: AS266418 - SERVTEL EIRELI, BR · not in PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

4Route objects not announced registered with origin AS266418, seen from no peer

Announced routes

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


2804:377c::/33	Valid	Nonecovered by 2804:377c::/32	351 55%	65
2804:377c:8000::/33	Valid	Nonecovered by 2804:377c::/32	351 55%	65
170.81.164.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
2804:377c::/32	Valid	Other IRR onlyRADB, TC	633 100%	67
170.81.164.0/23	Valid	Other IRR onlyRADB, TC	206 31%	56
170.81.166.0/23	Valid	Other IRR onlyRADB, TC	205 30%	56

AS-SET

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

Route object: none2
Route object: RIR4
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:377c::/33	No route object for it. A route object for 2804:377c::/32 with origin AS266418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266418 in the RIR database for the space.	351 of 636
Route object: none	2804:377c:8000::/33	No route object for it. A route object for 2804:377c::/32 with origin AS266418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266418 in the RIR database for the space.	351 of 636
Route object: RIR	170.81.164.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:377c::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	633 of 636
Route object: RIR	170.81.164.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	206 of 673
Route object: RIR	170.81.166.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	205 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:377c::/33

No route object for it. A route object for 2804:377c::/32 with origin AS266418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266418 in the RIR database for the space.

351 of 636

Route object: none

2804:377c:8000::/33

351 of 636

Route object: RIR

170.81.164.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

2804:377c::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

633 of 636

Route object: RIR

170.81.164.0/23

Route object only in RADB, TC. Add it in the RIR database for the space.

206 of 673

Route object: RIR

170.81.166.0/23

Route object only in RADB, TC. Add it in the RIR database for the space.

205 of 673

Route objects not announced

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


170.81.164.0/24	RADB, TC	Valid
170.81.165.0/24	RADB, TC	Valid
170.81.166.0/24	RADB, TC	Valid
170.81.167.0/24	RADB, TC	Valid

170.81.164.0/24

RADB, TC

Valid

170.81.165.0/24

RADB, TC

Valid

170.81.166.0/24

RADB, TC

Valid

170.81.167.0/24

RADB, TC

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.