Skip to content

Autonomous System

AS198057 · Flooyd Flooyd Telecom LTDA

Overview

AS198057 is announced on the Internet: RIPE RIS route collectors currently see 2 IPv4 prefixes and 18 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 512 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 10 upstream neighbours (transit providers or peers) and 2 downstream neighbours (customers or networks it carries). Its most visible upstreams are Sebastian Stefanek trading as MatHost.eu (AS214762), TESKE VIRTUAL SYSTEM LTDA (AS214331), and The Constant Company, LLC (AS20473). AS198057 was assigned by RIPE NCC, and its registration country is Brazil.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 17, 2026 at 1:17 AM UTC. This page is refreshed at most every 12 hours.

Go further

The trace goes to 2.27.246.1, the first address of 2.27.246.0/24. An address picked inside a prefix may not answer (nothing listens there, or the network filters probes): the trace then shows the path up to the last network that replies.

Announced prefixes

IPv4 prefixes (2 prefixes)

PrefixAddresses
2.27.246.0/24256
87.76.219.0/24256

IPv6 prefixes (18 prefixes)

Prefix
2a01:e281:ab00::/40
2a01:e281:ab01::/48
2a01:e281:ab02::/48
2a01:e281:ab03::/48
2a01:e281:ab04::/48
2a01:e281:ab05::/48
2a01:e281:ab06::/48
2a01:e281:ab07::/48
2a01:e281:ab10::/48
2a01:e281:ab11::/48
2a01:e281:ab12::/48
2a01:e281:ab15::/48
2a01:e281:ab22::/48
2a01:e281:ab23::/48
2a01:e281:ab24::/48
2a05:dfc1:7801::/48
2a05:dfc1:7812::/48
2a05:dfc1:7816::/48

Neighbours

Upstreams (transit or peers) (10)

ASNetworkVisibility
AS214762Sebastian Stefanek trading as MatHost.eu429
AS214331TESKE VIRTUAL SYSTEM LTDA333
AS20473The Constant Company, LLC259
AS28186ITS TELECOMUNICACOES LTDA256
AS11967Hop179 OU202
AS835GoCodeIT Inc45
AS267564FIBER TELECOM - TELECOMUNICACAO DE DADOS19
AS211509Rudakov Ihor4
AS62513GoCodeIT Inc1
AS205794JINZE YANG1

Downstreams (customers) (2)

ASNetworkVisibility
AS50763Robert McKay263
AS20473The Constant Company, LLC6

3 more neighbours appear on both sides of this network depending on the path, so they are counted in neither list.

Visibility is RIPEstat's count of how often the route collectors observed the link. It compares neighbours with each other; it is not a traffic volume.

How to read this page

An Autonomous System (AS) is a network run under one routing policy: an internet provider, a cloud, a content network, a university. Each one has a number, its ASN, assigned by a regional registry (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC), and uses BGP, the protocol networks use to tell each other where addresses are, to announce the blocks of addresses it delivers to.

A prefix such as 203.0.113.0/24 is a block of addresses: the number after the slash says how many bits are fixed, so a /24 holds 256 IPv4 addresses and a /16 holds 65,536. Networks often announce a large block and smaller pieces of it at the same time, which is why the address total counts each address once.

Neighbours come from the paths themselves. A network that appears just before this one in a path, on the collector's side, is an upstream: a transit provider or a peer. One that appears just after it is a downstream, usually a customer. Peering at an internet exchange also shows up as an upstream, so the upstream list is not a list of paid transit.

The data comes from RIPEstat, run by the RIPE NCC, which gathers the routing tables of hundreds of networks through its RIS route collectors. This page reads it when it is visited and keeps it for 12 hours at most; the BGP viewer reads it live.

Frequently asked questions

How do I find the ASN of an IP address?
Type the address in the BGP viewer: it shows the prefix that covers it, the AS that originates that prefix and the paths seen towards it. A traceroute also names the network of each hop, so you can see every AS a connection crosses.
Why does one company have several ASNs?
Large operators split their network by region, by activity or by history: a cloud may use one number for its backbone and another for a region, and every acquisition brings its own numbers. Each number has its own page, with its own prefixes and neighbours.
Why do prefix counts differ from one site to another?
Each source sees the routing table from different collectors, at a different time, and counts differently: some include prefixes withdrawn in recent weeks, some merge a block and its pieces. This page counts the prefixes RIPE RIS collectors see originated by the network at the end of the latest two-week window, and counts each IPv4 address once.
Is this the list of IP ranges of a cloud provider?
It is what its networks announce, which is what the Internet routes to them. Many providers also publish an official list of ranges per service and region; that list is the reference for firewall rules, because a range can be announced before it is used, or announced by another of their AS numbers.