bgpreport

Network · data from 2026-11-12

AS14447 Infinitron Global Communications

Registry name: INFINITRON-INTERNET-NET - Infinitron Internet LLC, US · PeeringDB

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

Announced routes

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

2a14:7581:9200::/40 Invalid: origin None 18 3%low visibility 12

AS-SET

PeeringDB's irr_as_set for AS14447: ARIN::AS-INFINITRON. 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 (AS14447 isn't in the set, or no route object for AS14447 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 objectsAS14447 in itNot covered
ARIN::AS-INFINITRON ARIN7 member sets in no database: AS-YUETAU, AS152848:AS-ASDFHK, AS201386:AS-MYMISAKA, AS208223:AS-ALL, AS209710:AS-SNRD-PEER … 3233,098 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 14 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • AS-SET: missing member7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin2a14:7581:9200::/40An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS14447 should announce it, add a ROA for AS14447.18 of 636
Route object: none2a14:7581:9200::/40No route object for it. Add a route object with origin AS14447 in the RIR database for the space.18 of 636
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS-YUETAU; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS152848:AS-ASDFHK; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS201386:AS-MYMISAKA; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS208223:AS-ALL; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS209710:AS-SNRD-PEER; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS214344:AS-AXNETS; no IRR database read has it.
AS-SET: missing memberARIN::AS-INFINITRONAS-INFINITRON (ARIN) lists AS59426:AS-DOWNSTREAM; no IRR database read has it.

Route objects not announced

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

23.141.244.0/24ARINInvalid: origin
2602:f613::/36ARINValid
2602:f613:20::/44ARINValid
2602:f613:f6::/48ARINValid
2a14:67c3:e0::/44RIPEValid

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.