bgpreport

Network · data from 2026-11-12

AS393670 Southern Fibernet

Registry name: SFC-GA - Southern Fibernet Corporation, US · PeeringDB

3IPv4 routes 33.3% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS393670, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS393670, 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.
38.46.52.0/23 No ROA Other IRR onlyRADB 671 100% 69
162.247.65.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
2604:36c0::/32 No ROA RIR databaseARIN, RADB 635 100% 69
216.66.12.0/23 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS393670: AS393670: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 (AS393670 isn't in the set, or no route object for AS393670 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.

NameDatabaseASNsSets Route objectsAS393670 in itNot covered
AS393670:AS-ALL RADB 2247 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 4 are in fix.csv.

  • ROA: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.46.52.0/23No ROA covers it. Add a ROA for AS393670, maxLength 23.671 of 673
Route object: RIR38.46.52.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.247.65.0/24No ROA covers it. Add a ROA for AS393670, maxLength 24.671 of 673
ROA: none2604:36c0::/32No ROA covers it. Add a ROA for AS393670, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS393670 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.