Network · data from 2026-11-12
AS61620 flowspec solutions ltda
Registry name: AS61620 - FLOWSPEC SOLUTIONS, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61620, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 179.0.83.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2804:90d0::/32 | Valid | Other IRR onlyTC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS61620: AS61620:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61620 isn't in the set, or no route object for AS61620 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS61620 in it | Not covered |
|---|---|---|---|---|---|
| AS61620:AS-ALL | TC | 55 | 6 | Yes | 1 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 179.0.83.0/24 | ROAs covering it name AS271331, not AS61620. If AS61620 should announce it, add a ROA for AS61620. |
| Route object: none | 179.0.83.0/24 | Route objects for it name AS271331. Add a route object with origin AS61620 in the RIR database for the space. |
| Route object: RIR | 2804:90d0::/32 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS61620 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.