Skip to main content

AS212983

METANNET-AS

------------------------UPLINKS------------------------

Registry

Authoritative registration data

AS number
212983
Name
METANNET-AS
Organisation
------------------------UPLINKS------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS212983
45.95.188.0/24 IPv4 /24 not checked
94.131.194.0/24 IPv4 /24 not checked
2001:67c:1308::/48 IPv6 /48 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 AS212983
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4 · IPv6
Giganet IXN: Global exchange 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 AS212983 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS212983 in AS paths

Observed upstreams
Families
AS35297 DATALINE-AS 304 548
v4 v6
AS6768 EUROTEL-AS 243 521
v4 v6
AS39199 RADIONET 25 52
v4
AS48648 KYIVLINK 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS212983 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 15
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS48919 UA-CITY-AS 1 3
v4 v6
AS209823 ENKI-AS 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.