Skip to main content

AS8629

MCNTT-AS

MCNTT Autonomous System

Registry

Authoritative registration data

AS number
8629
Name
MCNTT-AS
Organisation
MCNTT Autonomous System
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS8629
84.253.96.0/19 IPv4 /19 not checked
195.28.32.0/20 IPv4 /20 not checked

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS8629 in AS paths

Observed upstreams
Families
AS42610 NCNET-AS 276 362
v4
AS12389 ROSTELECOM-AS 186 233
v4
AS3216 SOVAM-AS 81 115
v4
AS25091 IP-Max 3 6
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS8629 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS28910 INTAL-ASN 1 1
v4
AS28917 Fiord-AS 1 1
v4
AS35598 INETCOM 1 1
v4
AS36236 NETACTUATE 1 1
v4
AS41327 FIBERTELECOM-AS 1 1
v4
AS41722 MIRAN-AS 1 1
v4
AS49673 TRUENETWORK 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.