Skip to main content

AS24748

THINX_Poland

THINX Internet exchange

Registry

Authoritative registration data

AS number
24748
Name
THINX_Poland
Organisation
THINX Internet exchange
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS24748
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 100,000 Mbps IPv4 · IPv6
Equinix Warsaw 20,000 Mbps IPv4 · IPv6
NL-ix: Main 100,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 AS24748 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS24748 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 257 626
v6
AS29632 NASSIST-AS 75 128
v6
AS20485 TRANSTELECOM 5 25
v4
AS20473 AS-VULTR 14 20
v6
AS8220 COLT 2 2
v6
AS13194 BITE 2 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

79 networks seen after AS24748 in AS paths

Observed downstreams
Families
AS39507 IPIVISION-AS 49 295
v6
AS15967 NETARTGROUP 163 277
v6
AS205581 CVD 4 68
v4 v6
AS5526 GENERACJApl-WR-IX-Exchange-Point 2 66
v4
AS57789 HOMENET 38 45
v6
AS15694 ATMAN-ISP-AS 21 31
v4 v6
AS201966 OPTIKABELPL 2 31
v4
AS39603 P4NET 4 24
v4
AS13000 LEON-AS 2 21
v4 v6
AS202053 UPCLOUD 2 21
v4 v6
AS57811 RedgeTechnologies 14 20
v6
AS201112 awhost 4 20
v4 v6
AS42 WOODYNET-1 1 17
v6
AS31080 O2-AS 1 16
v4
AS31608 GAWEX-AS 1 16
v4
AS24929 ITARTE 3 14
v4
AS42402 RIZNET-AS2 3 14
v4
AS396986 BYTEDANCE 3 14
v6
AS8308 NASK-COMMERCIAL 4 12
v6
AS49715 PL-WLANTECH-AS 2 12
v4
AS199524 GCORE 2 12
v6
AS197155 ARTNET 8 11
v6
AS8323 CYFRONET-AS2 6 11
v4 v6
AS24723 ATMAN-OFFICE-INTERNET-AS 6 10
v4 v6
AS48896 DHOSTING-AS 4 10
v4 v6
AS214762 MATHOST 8 9
v4
AS205160 DZP 4 9
v4 v6
AS202081 GOG 2 9
v4
AS43941 BAUER-AS 2 8
v4
AS215514 KEMPNET 2 8
v4
AS197431 GEMIUS-NETWORK 4 7
v4 v6
AS205308 ITI_Neovision 3 7
v4
AS57613 ESNET 1 7
v4
AS35434 PIRXNET-AS 3 6
v4 v6
AS33951 FORWEB 2 6
v4
AS41930 INITZERO-AS 2 6
v4
AS44655 METROLINE-AS 2 6
v4 v6
AS201434 CITYSTRADAPL-AS 5 5
v6
AS41247 SISQ 2 4
v4
AS42576 INTRSC-AS 2 4
v4
AS57966 INTRATEL-AS 2 4
v4
AS60399 ADAMPOLNET 2 4
v4
AS214666 CELLNEX-Poland 2 4
v4 v6
AS31505 DUNA-AS 1 4
v4
AS21344 PKO_BP 3 3
v6
AS62165 ASN-HOSTDIRECT 3 3
v4 v6
AS205727 ARUBAPL-AS 1 3
v4
AS6507 RIOT-NA1 2 2
v6
AS9085 SUPERMEDIA-AS 2 2
v4
AS42830 TVSAT364-AS 2 2
v6
AS198235 GRAKOM-AS 2 2
v6
AS200437 kbto 2 2
v6
AS202520 SKYPASS-AS 2 2
v6
AS211655 NASK-DNS-ANYCAST2 2 2
v6
AS48428 DPD-AS 1 2
v4
AS57239 NoBo_Quality 1 2
v4
AS198595 FOCUS-AS 1 2
v4
AS5550 TASK-AS 1 1
v6
AS8664 ICM-PUB 1 1
v6
AS12827 WirtualnaPolska 1 1
v4
AS13119 ACI-COM-AS 1 1
v6
AS25506 TVP-AS 1 1
v4
AS30975 TKK 1 1
v4
AS39661 DNB-AS 1 1
v4
AS50333 ELEKTRON 1 1
v4
AS50467 BESKID-MEDIA-AS 1 1
v6
AS50889 GFN-EMEA 1 1
v4
AS51465 FIXMAP-M3NET-TRANSIT 1 1
v4
AS51484 BLOKOWE 1 1
v6
AS57305 COMARCH-AS 1 1
v4
AS196999 Nestbank 1 1
v4
AS197399 MIASTO_KOSZALIN 1 1
v4
AS197977 SOLARISBUS 1 1
v4
AS198884 RAINBOWTOURS-PL-AS 1 1
v4
AS198921 UNIXSTORM-AS 1 1
v4
AS201342 ERGONET1 1 1
v4
AS202162 iMad 1 1
v4
AS206019 PKOLEASING 1 1
v4
AS219230 GRITMO 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 27 276
v4 v6
AS49544 i3Dnet 64 177
v4 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.