Skip to main content

AS203154

MITELIS-DOWNSTREAM

MITELIS SECURITY LIMITED

Registry

Authoritative registration data

AS number
203154
Name
MITELIS-DOWNSTREAM
Organisation
MITELIS SECURITY LIMITED
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS203154
177.3.210.0/24 IPv4 /24 RPKI valid
177.3.211.0/24 IPv4 /24 RPKI valid
194.87.156.0/24 IPv4 /24 not checked
2.26.4.0/24 IPv4 /24 RPKI valid
2.26.5.0/24 IPv4 /24 not checked
2.26.6.0/24 IPv4 /24 not checked
2.27.137.0/24 IPv4 /24 not checked
2.27.56.0/24 IPv4 /24 RPKI valid
31.76.25.0/24 IPv4 /24 RPKI valid
31.77.150.0/24 IPv4 /24 not checked
78.17.179.0/24 IPv4 /24 not checked
89.125.193.0/24 IPv4 /24 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS203154 in AS paths

Observed upstreams
Families
AS49581 TUBE-HOSTING 232 1,753
v4
AS58212 DATAFOREST 236 548
v4
AS215439 PLAY2GO-NET 229 548
v4
AS62255 BEMYLINK 225 276
v4
AS213229 MITELIS 231 272
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203154 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
AS49544 i3Dnet 1 1
v4
AS199524 GCORE 1 1
v4

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.