bgpreport

Network · data from 2026-11-12

AS142264 PT SKY BASE TECHNOLOGHY DIGITAL

Registry name: IDNIC-SKYBASE-ID - PT SKY BASE TECHNOLOGHY DIGITAL, ID · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS142264, seen from no peer

Announced routes

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

163.52.250.0/24 Valid Other IRR onlyRADB 670 100% 67
198.15.25.0/24 Valid Other IRR onlyRADB 670 100% 67
2001:df6:ac40::/48 Valid Other IRR onlyRADB 635 100% 68
2a13:9500:1e7::/48 Valid RIR databaseRIPE 633 100% 68

AS-SET

PeeringDB's irr_as_set for AS142264: AS142264:AS-SKY. 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 (AS142264 isn't in the set, or no route object for AS142264 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 objectsAS142264 in itNot covered
AS142264:AS-SKY 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 4 are in fix.csv.

  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR163.52.250.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR198.15.25.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2001:df6:ac40::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS142264:AS-SKYPeeringDB names AS142264:AS-SKY; no IRR database read has it.

Route objects not announced

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