Network · data from 2026-11-12
AS2728 GIGSOUTH
Registry name: GIGSOUTH - Gigsouth, LLC, US · PeeringDB
14IPv4 routes
100.0% RPKI valid · 14.3% with a route object
10IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS2728, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS2728, 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.
| 131.143.232.0/24 | Valid | Nonecovered by 131.143.232.0/23 | 666 99% |
| 131.143.233.0/24 | Valid | Nonecovered by 131.143.232.0/23 | 666 99% |
| 162.255.88.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.89.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.90.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.91.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.92.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.93.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.94.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 162.255.95.0/24 | Valid | Nonecovered by 162.255.88.0/21 | 666 99% |
| 199.185.174.0/24 | Valid | Nonecovered by 199.185.174.0/23 | 666 99% |
| 199.185.175.0/24 | Valid | Nonecovered by 199.185.174.0/23 | 666 99% |
| 2605:7b80::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:400::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:800::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:c00::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:1000::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:1400::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:1800::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:1c00::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:2000::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 2605:7b80:2400::/38 | Valid | Nonecovered by 2605:7b80::/32 | 631 99% |
| 162.255.88.0/21 | Valid | RIR databaseARIN, RADB | 666 99% |
| 199.185.174.0/23 | Valid | RIR databaseARIN, RADB | 666 99% |
AS-SET
PeeringDB's irr_as_set for AS2728: ARIN::AS2728: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 (AS2728 isn't in the set, or no route object for AS2728 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 | AS2728 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS2728:AS-ALL | ARIN | 4 | 2 | 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 25 are in fix.csv.
- Route object: none22
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.143.232.0/24 | No route object for it. A route object for 131.143.232.0/23 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 131.143.233.0/24 | No route object for it. A route object for 131.143.232.0/23 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.88.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.89.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.90.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.91.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.92.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.93.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.94.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 162.255.95.0/24 | No route object for it. A route object for 162.255.88.0/21 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 199.185.174.0/24 | No route object for it. A route object for 199.185.174.0/23 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 199.185.175.0/24 | No route object for it. A route object for 199.185.174.0/23 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:400::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:800::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:c00::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:1000::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:1400::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:1800::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:1c00::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:2000::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
| Route object: none | 2605:7b80:2400::/38 | No route object for it. A route object for 2605:7b80::/32 with origin AS2728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2728 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2728 whose prefix no peer sees AS2728 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.143.232.0/23 | ARIN | Valid |
| 2001:470:237::/48 | ARIN | Valid |
| 2605:7b80::/32 | ARIN, RADB | Valid |
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.