bgpreport

Network · data from 2026-11-12

AS268876 Ce Tech

Registry name: AS268876 - CE TECH INTERNET LTDA, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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 AS268876, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268876, 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.171.122.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
45.171.122.0/24 Valid Other IRR onlyTC 671 100% 67
45.171.123.0/24 Valid Other IRR onlyTC 671 100% 67
2804:5be8::/32 Valid Other IRR onlyRADB, TC 630 99% 67
2804:5be8::/33 Valid Other IRR onlyRADB, TC 630 99% 67
2804:5be8::/34 Valid Other IRR onlyTC 630 99% 67
2804:5be8:4000::/34 Valid Other IRR onlyTC 630 99% 67
2804:5be8:8000::/33 Valid Other IRR onlyRADB, TC 630 99% 67
2804:5be8:8000::/34 Valid Other IRR onlyTC 630 99% 67
2804:5be8:c000::/34 Valid Other IRR onlyTC 630 99% 67

AS-SET

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

  • Route object: RIR10
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR45.171.122.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.171.122.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.171.123.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:5be8::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8::/33Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8:4000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8:8000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:5be8:c000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
AS-SET: not foundAS-268876PeeringDB names AS-268876; no IRR database read has it.

Route objects not announced

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