Skip to main content

AS13058

serve-u-AS

ORG-KIEZ1-RIPE

Registry

Authoritative registration data

AS number
13058
Name
serve-u-AS
Organisation
ORG-KIEZ1-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

9

Total announced

18

Announced prefixes

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

Prefixes announced by AS13058
185.240.52.0/22 IPv4 /22 not checked
185.240.52.0/24 IPv4 /24 not checked
185.240.53.0/24 IPv4 /24 not checked
185.240.54.0/24 IPv4 /24 not checked
185.240.55.0/24 IPv4 /24 not checked
192.108.73.0/24 IPv4 /24 not checked
192.108.90.0/24 IPv4 /24 not checked
192.70.141.0/24 IPv4 /24 not checked
192.70.149.0/24 IPv4 /24 not checked
2a0c:7280::/29 IPv6 /29 RPKI valid
2a0c:7280::/32 IPv6 /32 RPKI valid
2a0c:7281::/32 IPv6 /32 RPKI valid
2a0c:7282::/32 IPv6 /32 RPKI valid
2a0c:7283::/32 IPv6 /32 RPKI valid
2a0c:7284::/32 IPv6 /32 RPKI valid
2a0c:7285::/32 IPv6 /32 RPKI valid
2a0c:7286::/32 IPv6 /32 RPKI valid
2a0c:7287::/32 IPv6 /32 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 AS13058
Address families
BCIX: BCIX Peering LAN 20,000 Mbps IPv4 · IPv6
Community-IX 10,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 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 AS13058 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

30 networks seen before AS13058 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS13058 in AS paths

Observed downstreams
Families
AS35829 AUTHS 348 1,133
v4 v6
AS20488 KIEZ-AS 344 1,122
v4 v6
AS34171 SNAFU-LIG-AS 11 40
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

58 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 3 154
v4 v6
AS24482 SGGS-AS-AP 3 130
v4 v6
AS12779 ITGATE 3 88
v4 v6
AS14840 ASN14840 3 88
v4 v6
AS25091 IP-Max 3 66
v4 v6
AS15547 NETPLUS 3 55
v4 v6
AS47147 AS-ANX 3 55
v4 v6
AS8529 OMANTEL-AS 3 44
v4 v6
AS47692 NESSUS 3 44
v4 v6
AS49544 i3Dnet 3 44
v4 v6
AS51184 FONIRA 3 44
v4 v6
AS25160 VORBOSS 3 40
v4 v6
AS553 BELWUE 3 22
v4 v6
AS559 Switch 3 22
v4 v6
AS680 DFN 3 22
v4 v6
AS1828 UNITAS 3 22
v4 v6
AS3212 TELEMACH 3 22
v4 v6
AS3214 XTOM 3 22
v4 v6
AS8298 IPNG 3 22
v4 v6
AS8888 XTOM 3 22
v4 v6
AS20932 SIG-ST 3 22
v4 v6
AS25220 GLOBALNOC-AS 3 22
v4 v6
AS28917 Fiord-AS 3 22
v6
AS29140 HOSTSERVER-AS 3 22
v4 v6
AS29691 NINE 3 22
v4 v6
AS31510 IKB-AS 3 22
v4 v6
AS34177 CELESTE-AS 3 22
v4 v6
AS35360 GARGUNET 3 22
v4 v6
AS35710 WEBERCLOUD 3 22
v4
AS36236 NETACTUATE 3 22
v4 v6
AS41327 FIBERTELECOM-AS 3 22
v4 v6
AS42541 FIBERBY 3 22
v4 v6
AS45489 SLT-GLOBAL 3 22
v4 v6
AS48919 UA-CITY-AS 3 22
v4 v6
AS50629 LWLCOM 3 22
v4 v6
AS56987 AS-ABACLOUDA 3 22
v4 v6
AS58057 SECUREBIT 3 22
v4 v6
AS58299 OPENFACTORY-AS 3 22
v4 v6
AS64475 FREIFUNK-FRANKFURT 3 22
v4 v6
AS199524 GCORE 3 22
v4 v6
AS199938 NETZWERGE 3 22
v4 v6
AS209823 ENKI-AS 3 22
v4 v6
AS264479 ASN264479 3 22
v4 v6
AS14630 INVESCO 3 11
v4
AS35598 INETCOM 3 11
v4
AS44901 belcloud 3 11
v4
AS51185 MAINSTREAMING-AS 3 11
v6
AS56662 EUTPNET 3 11
v6
AS142271 DOUBLESQUARE-AS-AP 3 11
v4
AS198249 OPSONE 3 11
v6
AS205112 PHILUNET 3 11
v4
AS206356 Freifunk-Essen 3 11
v4
AS213151 CHRISELSEN 3 11
v6
AS213241 TECHIT 3 11
v6
AS17639 CONVERGE-AS 2 6
v4 v6
AS210937 Showfom 2 4
v4
AS20488 KIEZ-AS 1 3
v4 v6
AS35829 AUTHS 1 3
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.