bgpreport

Network · data from 2026-11-12

AS265335 PLANETA NET TELECOM

Registry name: AS265335 - PLANETA NET TELECOM, BR · PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
15Route objects not announced registered with origin AS265335, seen from no peer

Announced routes

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

168.181.12.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
187.63.123.0/24 Valid Other IRR onlyTC 672 100% 67
45.188.150.0/24 Valid Other IRR onlyALTDB, TC 671 100% 67
45.188.151.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
168.181.14.0/23 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
45.188.148.0/24 Valid Other IRR onlyTC 670 100% 67
45.188.149.0/24 Valid Other IRR onlyTC 670 100% 67
187.63.120.0/24 Valid Other IRR onlyTC 670 100% 67
168.181.12.0/23 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
187.63.121.0/24 Valid Other IRR onlyTC 668 99% 67
187.63.122.0/24 Valid Other IRR onlyALTDB, RADB, TC 668 99% 67
2804:2e44::/33 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
2804:2e44:8000::/33 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
2804:2e44:f700::/40 Valid Other IRR onlyRADB 636 100% 67
2804:2e44::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:2e44:f100::/40 Valid Other IRR onlyTC 631 99% 67
168.181.12.0/24 Valid Other IRR onlyRADB, TC 198 29% 56

AS-SET

PeeringDB's irr_as_set for AS265335: AS265335:AS-PLANETANET. 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 (AS265335 isn't in the set, or no route object for AS265335 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 objectsAS265335 in itNot covered
AS265335:AS-PLANETANET ALTDB 4259 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 32 are in fix.csv.

  • Route object: RIR17
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: RIR168.181.12.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.63.123.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.188.150.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.181.14.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.148.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.188.149.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR187.63.120.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR168.181.12.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.63.121.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR187.63.122.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:2e44::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2e44:8000::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2e44:f700::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2e44::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2e44:f100::/40Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR168.181.12.0/24Route object only in RADB, TC. Add it in the RIR database for the space.198 of 673

Route objects not announced

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

45.188.148.0/22ALTDB, RADB, TCValid
45.188.148.0/23ALTDB, TCValid
45.188.150.0/23TCValid
168.181.13.0/24RADB, TCValid
168.181.14.0/24RADB, TCValid
168.181.15.0/24RADB, TCValid
187.63.120.0/22ALTDB, RADB, TCValid
187.63.120.0/23TCValid
187.63.122.0/23TCValid
2804:2e44::/34RADBValid
2804:2e44:4000::/34RADBValid
2804:2e44:8000::/34RADBValid
2804:2e44:c000::/34RADBValid
2804:2e44:f000::/40TCValid
2804:2e44:f600::/40RADB, TCValid

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.