Skip to main content

AS199095

CITYMESH-AS

ORG-CN50-RIPE

Registry

Authoritative registration data

AS number
199095
Name
CITYMESH-AS
Organisation
ORG-CN50-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS199095
31.31.128.0/19 IPv4 /19 not checked
31.31.128.0/21 IPv4 /21 not checked
31.31.136.0/21 IPv4 /21 not checked
31.31.144.0/21 IPv4 /21 not checked
31.31.152.0/21 IPv4 /21 not checked
185.195.28.0/22 IPv4 /22 not checked
185.195.28.0/23 IPv4 /23 not checked
31.31.136.0/24 IPv4 /24 not checked
2a11:bfc0::/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 AS199095
Address families
BNIX 10,000 Mbps IPv4 · IPv6
NL-ix: Main — 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 AS199095 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS199095 in AS paths

Observed upstreams
Families
AS9031 EDPNETapp 315 1,925
v4 v6
AS42160 273 359
v4
AS6939 HURRICANE 95 287
v4 v6
AS25311 26 219
v4 v6
AS6461 ZAYO-6461 8 90
v4 v6
AS8218 NEO-ASN 3 65
v4 v6
AS34019 HIVANE 4 48
v4 v6
AS4455 2 12
v4
AS6696 VERIXI 1 8
v4 v6
AS39686 1 8
v4 v6
AS9009 M247 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199095 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS48185 team_blue 1 24
v4 v6
AS45049 1 8
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.