Skip to main content

AS210258

Wildanet

Wildanet Ltd

Registry

Authoritative registration data

AS number
210258
Name
Wildanet
Organisation
Wildanet Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

60

Total announced

70

Announced prefixes

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

Prefixes announced by AS210258
139.28.208.0/22 IPv4 /22 RPKI valid
185.254.148.0/22 IPv4 /22 not checked
139.28.208.0/24 IPv4 /24 not checked
139.28.209.0/24 IPv4 /24 RPKI valid
139.28.210.0/24 IPv4 /24 not checked
139.28.211.0/24 IPv4 /24 not checked
185.254.148.0/24 IPv4 /24 RPKI valid
185.254.149.0/24 IPv4 /24 not checked
185.254.150.0/24 IPv4 /24 not checked
185.254.151.0/24 IPv4 /24 not checked
2a0c:4f40::/29 IPv6 /29 RPKI valid
2a0c:4f46::/32 IPv6 /32 RPKI valid
2a0c:4f47::/32 IPv6 /32 RPKI valid
2a0c:4f46:4000::/34 IPv6 /34 RPKI valid
2a0c:4f46::/34 IPv6 /34 RPKI valid
2a0c:4f47:8000::/34 IPv6 /34 RPKI valid
2a0c:4f47::/34 IPv6 /34 not checked
2a0c:4f41:1000::/38 IPv6 /38 RPKI valid
2a0c:4f41:1400::/38 IPv6 /38 RPKI valid
2a0c:4f41:1800::/38 IPv6 /38 RPKI valid
2a0c:4f41:1c00::/38 IPv6 /38 not checked
2a0c:4f41:2000::/38 IPv6 /38 RPKI valid
2a0c:4f41:2400::/38 IPv6 /38 RPKI valid
2a0c:4f41:2800::/38 IPv6 /38 RPKI valid
2a0c:4f41:2c00::/38 IPv6 /38 RPKI valid
2a0c:4f41:3000::/38 IPv6 /38 RPKI valid
2a0c:4f41:3400::/38 IPv6 /38 RPKI valid
2a0c:4f41:3800::/38 IPv6 /38 RPKI valid
2a0c:4f41:3c00::/38 IPv6 /38 not checked
2a0c:4f41:4000::/38 IPv6 /38 RPKI valid
2a0c:4f41:400::/38 IPv6 /38 not checked
2a0c:4f41:4400::/38 IPv6 /38 RPKI valid
2a0c:4f41:4800::/38 IPv6 /38 RPKI valid
2a0c:4f41:4c00::/38 IPv6 /38 RPKI valid
2a0c:4f41:5000::/38 IPv6 /38 RPKI valid
2a0c:4f41:5400::/38 IPv6 /38 RPKI valid
2a0c:4f41:5800::/38 IPv6 /38 RPKI valid
2a0c:4f41:5c00::/38 IPv6 /38 RPKI valid
2a0c:4f41:6800::/38 IPv6 /38 RPKI valid
2a0c:4f41:7c00::/38 IPv6 /38 not checked
2a0c:4f41:8000::/38 IPv6 /38 RPKI valid
2a0c:4f41:800::/38 IPv6 /38 RPKI valid
2a0c:4f41:8400::/38 IPv6 /38 RPKI valid
2a0c:4f41:8800::/38 IPv6 /38 RPKI valid
2a0c:4f41:9000::/38 IPv6 /38 RPKI valid
2a0c:4f41:9400::/38 IPv6 /38 RPKI valid
2a0c:4f41::/38 IPv6 /38 RPKI valid
2a0c:4f41:c00::/38 IPv6 /38 not checked
2a0c:4f42:1c00::/38 IPv6 /38 RPKI valid
2a0c:4f42:2000::/38 IPv6 /38 RPKI valid
2a0c:4f42:2400::/38 IPv6 /38 RPKI valid
2a0c:4f42:2800::/38 IPv6 /38 RPKI valid
2a0c:4f42:2c00::/38 IPv6 /38 RPKI valid
2a0c:4f42:3000::/38 IPv6 /38 RPKI valid
2a0c:4f42:3400::/38 IPv6 /38 RPKI valid
2a0c:4f42:3800::/38 IPv6 /38 RPKI valid
2a0c:4f42:400::/38 IPv6 /38 RPKI valid
2a0c:4f42:4400::/38 IPv6 /38 RPKI valid
2a0c:4f42:4800::/38 IPv6 /38 RPKI valid
2a0c:4f42:4c00::/38 IPv6 /38 not checked
2a0c:4f42:5000::/38 IPv6 /38 RPKI valid
2a0c:4f42:5400::/38 IPv6 /38 RPKI valid
2a0c:4f42:5c00::/38 IPv6 /38 RPKI valid
2a0c:4f42:6800::/38 IPv6 /38 RPKI valid
2a0c:4f42:8000::/38 IPv6 /38 RPKI valid
2a0c:4f42:800::/38 IPv6 /38 not checked
2a0c:4f42:8800::/38 IPv6 /38 RPKI valid
2a0c:4f42:9000::/38 IPv6 /38 RPKI valid
2a0c:4f42::/38 IPv6 /38 RPKI valid
2a0c:4f42:c00::/38 IPv6 /38 RPKI valid

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 AS210258
Address families
LINX LON1: Main 100,000 Mbps IPv4 · IPv6
LINX LON2 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 AS210258 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

59 networks seen before AS210258 in AS paths

Observed upstreams
Families
AS24482 SGGS-AS-AP 2 774
v4 v6
AS33891 CORE-BACKBONE 12 546
v4 v6
AS25091 IP-Max 9 525
v4 v6
AS14840 ASN14840 2 345
v4 v6
AS174 COGENT-174 121 341
v4 v6
AS15802 DU-AS1 9 334
v4 v6
AS35280 F5 5 279
v4 v6
AS34549 MEER-AS 7 278
v4 v6
AS22356 ASN22356 7 240
v4 v6
AS3214 XTOM 4 187
v4 v6
AS12779 ITGATE 2 178
v4 v6
AS34927 iFog-GmbH 3 168
v4 v6
AS48362 TKSWF-AS 2 168
v4 v6
AS6461 ZAYO-6461 39 151
v4 v6
AS6939 HURRICANE 87 148
v4 v6
AS29075 IELO 4 123
v4 v6
AS20562 OPEN-PEERING-AS 3 115
v4 v6
AS6797 GLOBALCONNECT-NET 2 115
v4 v6
AS4455 BSO 2 85
v4 v6
AS6057 6057 2 84
v4 v6
AS37468 ORG-AC4-AFRINIC 3 81
v4 v6
AS8714 LINX-ROUTESRV 3 78
v4 v6
AS64049 RJIPL-SG 1 78
v4 v6
AS41327 FIBERTELECOM-AS 2 74
v4 v6
AS39120 CONVERGENZE-AS 1 66
v4 v6
AS7195 7195 1 59
v6
AS199995 OT-AS 1 58
v6
AS34177 CELESTE-AS 2 52
v4 v6
AS62275 NHM 2 47
v4 v6
AS55850 MERCURYNZ-AS-AP 1 41
v4 v6
AS21215 UGNI 1 39
v4 v6
AS61049 EXASCALE 2 35
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 34
v4
AS60171 AFRIX-AS 1 33
v4 v6
AS50304 BLIX 3 30
v4
AS8943 JUMP 12 28
v4 v6
AS21472 SERVERHOUSE 1 27
v6
AS39386 STC-IGW-AS 1 27
v6
AS215638 AS-CILIX-LIMITED 1 27
v6
AS3216 SOVAM-AS 3 24
v4
AS37497 ORG-NPL3-AFRINIC 2 20
v4
AS9044 SOLNET 1 20
v4
AS5405 INTERDOTLINK 6 19
v4 v6
AS37100 ORG-SL75-AFRINIC 2 18
v4
AS1267 ASN-WINDTRE 2 16
v4
AS9002 RETN-AS 10 15
v6
AS3741 ORG-DD1-AFRINIC 1 10
v4
AS6204 ZET-NET 1 10
v4
AS15412 FLAG-AS 1 10
v4
AS15958 CETIN_doo_AS 1 10
v4
AS1031 PEER1-1031 1 8
v4
AS4657 STARHUB-INTERNET 1 8
v4
AS6206 NETROUTING-AS 1 8
v4
AS7713 telkomnet-as-ap 1 8
v4
AS9930 TTNET-MY 1 8
v4
AS17557 PKTELECOM-AS-PK 1 8
v4
AS58453 CMI-INT-HK 1 8
v4
AS61568 ASN61568 1 8
v4
AS31500 GNM-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS210258 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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