Skip to main content

AS41230

ASK4

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

Registry

Authoritative registration data

AS number
41230
Name
ASK4
Organisation
===========================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

7

Total announced

23

Announced prefixes

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

Prefixes announced by AS41230
31.205.0.0/16 IPv4 /16 RPKI valid
31.205.192.0/18 IPv4 /18 not checked
31.205.64.0/18 IPv4 /18 RPKI valid
213.143.0.0/19 IPv4 /19 not checked
78.109.176.0/20 IPv4 /20 not checked
81.23.48.0/20 IPv4 /20 RPKI valid
185.134.128.0/22 IPv4 /22 RPKI valid
185.134.136.0/22 IPv4 /22 RPKI valid
185.134.144.0/22 IPv4 /22 RPKI valid
185.198.228.0/22 IPv4 /22 not checked
45.154.248.0/22 IPv4 /22 RPKI valid
45.81.120.0/22 IPv4 /22 not checked
185.134.136.0/23 IPv4 /23 not checked
176.119.145.0/24 IPv4 /24 RPKI valid
185.134.138.0/24 IPv4 /24 RPKI valid
185.134.139.0/24 IPv4 /24 RPKI valid
2a00:1a10::/29 IPv6 /29 RPKI valid
2a07:c300::/29 IPv6 /29 not checked
2a0e:2a40::/29 IPv6 /29 RPKI valid
2a0e:2ac0::/29 IPv6 /29 not checked
2a0e:5680::/29 IPv6 /29 RPKI valid
2a0f:dd00::/29 IPv6 /29 RPKI valid
2a10:d00::/29 IPv6 /29 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 AS41230
Address families
IXLeeds 10,000 Mbps IPv4 · IPv6
LINX LON1: Main 100,000 Mbps IPv4 · IPv6
LINX Manchester 30,000 Mbps IPv4 · IPv6
LONAP: LON0 100,000 Mbps IPv4 · IPv6
MegaIX Dusseldorf 10,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 AS41230 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

53 networks seen before AS41230 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 421 4,033
v4 v6
AS2914 NTT-DATA-2914 389 2,467
v4 v6
AS6939 HURRICANE 226 1,235
v4 v6
AS8218 NEO-ASN 15 426
v4 v6
AS25091 IP-Max 34 267
v4
AS14840 ASN14840 17 253
v4 v6
AS34549 MEER-AS 40 228
v4
AS6461 ZAYO-6461 59 217
v4 v6
AS13030 INIT7 27 216
v4
AS34927 iFog-GmbH 23 199
v4 v6
AS33891 CORE-BACKBONE 24 174
v4 v6
AS12779 ITGATE 12 170
v4
AS48362 TKSWF-AS 15 150
v4
AS50304 BLIX 23 106
v4
AS3214 XTOM 10 96
v4
AS39351 ESAB-AS 16 86
v4 v6
AS4455 BSO 12 83
v4 v6
AS37497 ORG-NPL3-AFRINIC 15 74
v4
AS8455 ATOM86-AS 14 72
v4
AS60068 CDN77 10 67
v4 v6
AS20562 OPEN-PEERING-AS 16 61
v4 v6
AS6797 GLOBALCONNECT-NET 7 60
v4
AS5405 INTERDOTLINK 14 58
v4
AS41327 FIBERTELECOM-AS 12 56
v4
AS9044 SOLNET 6 56
v4
AS4637 ASN-TELSTRA-GLOBAL 12 49
v4
AS35280 F5 10 48
v4
AS3303 SWISSCOM 10 45
v4
AS29075 IELO 10 44
v4
AS4657 STARHUB-INTERNET 8 38
v4
AS15958 CETIN_doo_AS 8 38
v4
AS55850 MERCURYNZ-AS-AP 8 38
v4
AS15802 DU-AS1 8 37
v4
AS6057 6057 8 36
v4
AS1267 ASN-WINDTRE 7 34
v4
AS22356 ASN22356 15 32
v4 v6
AS37468 ORG-AC4-AFRINIC 8 30
v4
AS3741 ORG-DD1-AFRINIC 7 30
v4
AS6204 ZET-NET 9 29
v4
AS1031 PEER1-1031 4 24
v4
AS37100 ORG-SL75-AFRINIC 4 22
v4
AS8220 COLT 4 19
v4 v6
AS3216 SOVAM-AS 4 18
v4
AS61568 ASN61568 4 18
v4
AS60171 AFRIX-AS 3 16
v4
AS24961 MYLOC-AS 2 16
v4
AS9009 M247 2 12
v4
AS7195 7195 2 11
v4
AS137409 GSLNETWORKS-AS-AP 10 10
v4
AS21215 UGNI 2 7
v4
AS21472 SERVERHOUSE 2 2
v4
AS39120 CONVERGENZE-AS 2 2
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS41230 in AS paths

Observed downstreams
Families
AS8916 PORTFAST 301 2,235
v4 v6
AS30933 PROTEXIA-EU 269 2,029
v4
AS206049 COMMUNICATE 440 1,592
v4 v6
AS21396 NETCONNEX 79 899
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

38 adjacencies that may be an artefact of collector peering

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.