ResearchRouting table, RPKI, IRR & looking glass

AS201719 Teleklik d.o.o.

AS201719 (TK-AS) is registered to Teleklik d.o.o. in BA. It originates 6 prefixes in the global routing table.

6
IPv4 prefixes
0
IPv6 prefixes
1,280
IPv4 addresses
100%
RPKI valid

Who holds AS201719

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS201719
Handle
TK-AS
Organization
Teleklik d.o.o.
Country
BA
ASPA
3 providers

What AS201719 announces

Prefixes originated by AS201719 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
6
IPv6 prefixes
0
IPv4 addresses
1,280 (5 /24s)
RPKI valid
6 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS201719
7
With an IRR route object
6 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

Who AS201719 buys transit from

Inferred from the AS paths in the RouteViews tables, refreshed every 4 hours, most-seen first. 3 upstreams; those marked ASPA are also named in its ASPA.

Who buys transit from AS201719

None seen: AS201719 does not appear to provide transit to anyone.

Provider authorization

AS201719 publishes an ASPA naming these providers. Check a path.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPETK-ASRIPE-NCC-END-MNT, TELEKLIK-MNT

Route objects with origin AS201719: RIPE 7

as-sets that list AS201719 (8)