Network · data from 2026-11-12
AS28584 DSI Internet
Registry name: AS28584 - Defferrari Solucoes em Internet Ltda, BR · PeeringDB
45IPv4 routes
100.0% RPKI valid · 97.8% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
1 with no route object for this origin
26Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS28584, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS28584, 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.
| 200.159.166.0/24 | Valid | Nonecovered by 200.159.166.0/23 | 671 100% |
| 131.72.80.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.129.236.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.39.160.0/21 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.129.232.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 200.159.160.0/20 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 200.159.160.0/21 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.160.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.168.0/21 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.168.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.176.0/20 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 200.159.176.0/21 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.180.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.184.0/21 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.184.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.188.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 200.159.164.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 200.159.172.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 200.159.176.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 2804:918::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 131.72.80.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 131.72.82.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.39.160.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.39.162.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.39.164.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.39.166.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.129.232.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.129.234.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.129.236.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 177.129.238.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.160.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.162.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.164.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.166.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.168.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.170.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.172.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.174.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.176.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.178.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.180.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.182.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.184.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.186.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.188.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
| 200.159.190.0/23 | Valid | Other IRR onlyTC | 9 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS28584: AS28584:AS-DSI. 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 (AS28584 isn't in the set, or no route object for AS28584 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 | AS28584 in it | Not covered |
|---|---|---|---|---|---|
| AS28584:AS-DSI | TC | 1 | 1 | Yes | 0 |
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 46 are in fix.csv.
- Route object: none1
- Route object: RIR45
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.159.166.0/24 | No route object for it. A route object for 200.159.166.0/23 with origin AS28584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28584 in the RIR database for the space. |
| Route object: RIR | 131.72.80.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.236.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.160.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.232.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.160.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.160.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.160.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.168.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.168.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.176.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.176.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.180.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.184.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.184.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.188.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.164.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.172.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.176.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:918::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.80.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.82.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.160.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.162.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.164.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.166.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.232.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.234.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.236.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.129.238.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.160.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.162.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.164.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.166.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.168.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.170.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.172.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.174.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.176.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.178.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.180.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.182.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.184.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.186.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.188.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.159.190.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS28584 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.