Network · data from 2026-11-12

AS60733 PERKE

Registry name: PERKE-NET ZORAN PEROVIC trading as Agencija Perke.NET, RS · PeeringDB

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

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

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

2Route objects not announced registered with origin AS60733, seen from no peer

Announced routes

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


88.218.137.0/24	Valid	RIR databaseRIPE	671 100%	68
88.218.138.0/24	Valid	RIR databaseRIPE	671 100%	68
88.218.136.0/24	Valid	RIR databaseRIPE	667 99%	67
2a09:ab80::/29	Valid	RIR databaseRIPE	634 100%	69

AS-SET

PeeringDB's irr_as_set for AS60733: RIPE::AS60733 RIPE::AS13004 RIPE::AS60733:AS-PN-TO-GOOGLE. 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 (AS60733 isn't in the set, or no route object for AS60733 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.

Name	Database	ASNs	Sets	Route objects	AS60733 in it	Not covered
RIPE::AS60733	A single AS number, not a set: AS60733 (this network), 6 route objects.
RIPE::AS13004	A single AS number, not a set: AS13004, 6 route objects.
RIPE::AS60733:AS-PN-TO-GOOGLE	RIPE1 member set in no database: AS44477:AS-DOWNSTREAMS	98	8	2,105	Yes	0

Name

Database

ASNs

Sets

Route objects

AS60733 in it

Not covered

RIPE::AS60733

A single AS number, not a set: AS60733 (this network), 6 route objects.

RIPE::AS13004

A single AS number, not a set: AS13004, 6 route objects.

RIPE::AS60733:AS-PN-TO-GOOGLE

RIPE1 member set in no database: AS44477:AS-DOWNSTREAMS

2,105

Yes

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.

AS-SET: missing member1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
AS-SET: missing member	RIPE::AS60733:AS-PN-TO-GOOGLE	AS60733:AS-PN-TO-GOOGLE (RIPE) lists AS44477:AS-DOWNSTREAMS; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

RIPE::AS60733:AS-PN-TO-GOOGLE

AS60733:AS-PN-TO-GOOGLE (RIPE) lists AS44477:AS-DOWNSTREAMS; no IRR database read has it.

Route objects not announced

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


88.218.136.0/22	RIPE	Valid
88.218.139.0/24	RIPE	Valid

88.218.136.0/22

RIPE

Valid

88.218.139.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.