Skip to main content

AS199837

TREPSYSTEMAS

*** CUSTOMER TRIVENET ***

Registry

Authoritative registration data

AS number
199837
Name
TREPSYSTEMAS
Organisation
*** CUSTOMER TRIVENET ***
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS199837
185.128.148.0/22 IPv4 /22 not checked
185.249.12.0/22 IPv4 /22 not checked
185.44.212.0/22 IPv4 /22 not checked
77.83.216.0/22 IPv4 /22 not checked
185.249.12.0/24 IPv4 /24 not checked
185.249.13.0/24 IPv4 /24 not checked
185.249.14.0/24 IPv4 /24 not checked
185.249.15.0/24 IPv4 /24 not checked
2a04:9f00::/29 IPv6 /29 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 AS199837
Address families
MIX-IT 10,000 Mbps IPv4 · IPv6
TOP-IX: Public Peering VLAN 40,000 Mbps IPv4 · IPv6
VSIX: Primary 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 AS199837 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS199837 in AS paths

Observed upstreams
Families
AS47927 WIFIWEB 145 1,385
v4
AS9002 RETN-AS 85 623
v4
AS3356 LEVEL3 64 544
v4 v6
AS6939 HURRICANE 216 377
v4 v6
AS3303 SWISSCOM 5 48
v4
AS4455 BSO 3 27
v4
AS5405 INTERDOTLINK 2 17
v4 v6
AS14840 ASN14840 2 15
v4
AS31543 MYNET-AS 1 8
v4
AS25091 IP-Max 3 5
v6
AS29632 NASSIST-AS 3 3
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS199837 in AS paths

Observed downstreams
Families
AS12481 49 208
v4

No rows match “”.

Showing of

Uncertain adjacencies

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