bgpreport

Network · data from 2026-11-12

AS139073 Fantasy Sky Internet eXchange

Registry name: FSIX-AS-AP - Fantasy Sky Internet eXchange, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139073, 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.

44.31.96.0/24 No ROA Other IRR onlyRADB 672 100% 67
2402:e380:117::/48 Valid Nonecovered by 2402:e380:110::/44 635 100% 68
2402:e380:110::/44 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:112::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:114::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:118::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:11e::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:126::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:12c::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:133::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:137::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:138::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:13c::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:13e::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:141::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:142::/48 Valid Other IRR onlyALTDB 635 100% 68
2402:e380:100::/40 Valid RIR databaseALTDB, APNIC, RADB 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS139073: AS-FSIX. 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 (AS139073 isn't in the set, or no route object for AS139073 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 objectsAS139073 in itNot covered
AS-FSIX RIPE 1121 Yes 0
ALTDB (also) 1121 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 22 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR15
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none44.31.96.0/24No ROA covers it. Add a ROA for AS139073, maxLength 24.672 of 673
Route object: RIR44.31.96.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2402:e380:117::/48No route object for it. A route object for 2402:e380:110::/44 with origin AS139073 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139073 in the RIR database for the space.635 of 636
Route object: RIR2402:e380:110::/44Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:112::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:114::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:118::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:11e::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:126::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:12c::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:133::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:137::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:138::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:13c::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:13e::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:141::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:e380:142::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS139073 whose prefix no peer sees AS139073 announce. Many are kept on purpose (backup routes, space announced only in some places).

2402:e380:119::/48ALTDBValid
2402:e380:13b::/48ALTDBValid
2402:e380:13f::/48ALTDBValid
2402:e380:140::/48ALTDBValid
2402:e380:312::/48APNICNo ROA

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.