Skip to main content

AS213286

VERVETECHPK

==================================================

Registry

Authoritative registration data

AS number
213286
Name
VERVETECHPK
Organisation
==================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS213286
2a10:2f00:131::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS213286
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS213286 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS213286 in AS paths

Observed upstreams
Families
AS212895 ROUTE64_ORG 94 115
v6
AS34872 Servperso_Systems 26 33
v6
AS20473 AS-VULTR 21 24
v6
AS25091 IP-Max 2 2
v6
AS401753 BIXCE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS213286 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS199854 ITBYPASSION 1 1
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.