bgpreport

Network · data from 2026-11-12

AS266959 SKYINF SOLUCOES EM TECNOLOGIA DE INFORMACAO LTDA

Registry name: AS266959 - SKYINF SOLUCOES EM TECNOLOGIA DE INFORMACAO LTDA, BR · PeeringDB

7IPv4 routes 0.0% 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
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266959, seen from no peer

Announced routes

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

45.225.164.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
45.225.164.0/23 No ROA Other IRR onlyTC 669 99% 67
45.225.166.0/23 No ROA Other IRR onlyTC 669 99% 67
45.225.164.0/24 No ROA Other IRR onlyTC 668 99% 67
45.225.165.0/24 No ROA Other IRR onlyTC 668 99% 67
45.225.166.0/24 No ROA Other IRR onlyTC 668 99% 67
45.225.167.0/24 No ROA Other IRR onlyTC 668 99% 67
2804:45fc::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS266959: TC::AS-SKYINF. 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 (AS266959 isn't in the set, or no route object for AS266959 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 objectsAS266959 in itNot covered
TC::AS-SKYINF In no IRR database read today.

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 17 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none45.225.164.0/22No ROA covers it. Add a ROA for AS266959, maxLength 22.672 of 673
Route object: RIR45.225.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.225.164.0/23No ROA covers it. Add a ROA for AS266959, maxLength 23.669 of 673
Route object: RIR45.225.164.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none45.225.166.0/23No ROA covers it. Add a ROA for AS266959, maxLength 23.669 of 673
Route object: RIR45.225.166.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none45.225.164.0/24No ROA covers it. Add a ROA for AS266959, maxLength 24.668 of 673
Route object: RIR45.225.164.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none45.225.165.0/24No ROA covers it. Add a ROA for AS266959, maxLength 24.668 of 673
Route object: RIR45.225.165.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none45.225.166.0/24No ROA covers it. Add a ROA for AS266959, maxLength 24.668 of 673
Route object: RIR45.225.166.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none45.225.167.0/24No ROA covers it. Add a ROA for AS266959, maxLength 24.668 of 673
Route object: RIR45.225.167.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:45fc::/32No ROA covers it. Add a ROA for AS266959, maxLength 32.634 of 636
Route object: RIR2804:45fc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
AS-SET: not foundTC::AS-SKYINFPeeringDB names TC::AS-SKYINF; no IRR database read has it.

Route objects not announced

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