Skip to main content

AS43667

VRMNT-AS

=============================================

Registry

Authoritative registration data

AS number
43667
Name
VRMNT-AS
Organisation
=============================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS43667
77.91.192.0/21 IPv4 /21 not checked
94.198.128.0/21 IPv4 /21 not checked
185.32.132.0/22 IPv4 /22 not checked
185.32.134.0/24 IPv4 /24 not checked
185.32.135.0/24 IPv4 /24 not checked
45.152.123.0/24 IPv4 /24 not checked
77.91.198.0/24 IPv4 /24 not checked
94.198.131.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS43667 in AS paths

Observed upstreams
Families
AS48347 MTW-AS 302 1,202
v4
AS20764 RASCOM-AS 111 670
v4
AS29076 CITYTELECOM-AS 85 629
v4
AS1299 TWELVE99 69 378
v4
AS25091 IP-Max 5 51
v4
AS6939 HURRICANE 16 34
v4
AS41327 FIBERTELECOM-AS 2 9
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS43667 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

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