Skip to main content

AS199713

MLL-AS

MLL Telecom Ltd.

Registry

Authoritative registration data

AS number
199713
Name
MLL-AS
Organisation
MLL Telecom Ltd.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

0

Total announced

16

Announced prefixes

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

Prefixes announced by AS199713
217.30.24.0/21 IPv4 /21 not checked
5.255.48.0/21 IPv4 /21 not checked
138.124.224.0/22 IPv4 /22 not checked
138.124.236.0/22 IPv4 /22 not checked
185.100.88.0/22 IPv4 /22 not checked
185.17.96.0/22 IPv4 /22 not checked
185.22.4.0/22 IPv4 /22 not checked
185.49.36.0/22 IPv4 /22 not checked
213.178.132.0/22 IPv4 /22 not checked
91.196.28.0/22 IPv4 /22 not checked
94.101.172.0/22 IPv4 /22 not checked
94.198.172.0/22 IPv4 /22 not checked
91.231.90.0/23 IPv4 /23 not checked
194.140.226.0/24 IPv4 /24 not checked
194.26.206.0/24 IPv4 /24 not checked
194.61.79.0/24 IPv4 /24 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 AS199713
Address families
LINX LON1: Main 20,000 Mbps IPv4
LINX Manchester 20,000 Mbps IPv4
LONAP: LON0 10,000 Mbps IPv4

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 AS199713 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

27 networks seen before AS199713 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS199713 in AS paths

Observed downstreams
Families
AS49728 HEREFORDSHIRE-COUNCIL 148 170
v4
AS197370 NOTTSCC 147 170
v4
AS49247 ESFRS 145 170
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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